some random start-up warnings that i'd like to fix

[josolanes]

here are the warnings:

* /etc/init.d/serial missing; skipping
* System.map not found

the errors might not be complete, but that's what i remember out of them....that's definately the important part

how would i go about fixing them? the /etc/init.d/serial one hasn't shown any noticeable problems on my system (what does it do anyways?), but the System.map one has shown up in a couple of compiles and has given me some problems.

please help...
Thanks in advance!

[nalg0rath]

To remove the '* /etc/init.d/serial missing; skipping' run:

# rc-update del serial boot

or:

# rm /etc/runlevels/boot/serial

If you have not compiled a new kernel since you compled the one you're using now, run:

# mv /usr/src/linux/System.map /boot/System.map-$(uname -r)

[josolanes]

To remove the '* /etc/init.d/serial missing; skipping' run:

# rc-update del serial boot

or:

# rm /etc/runlevels/boot/serial

If you have not compiled a new kernel since you compled the one you're using now, run:

# mv /usr/src/linux/System.map /boot/System.map-$(uname -r)

ok..the first one worked fine, but the one regarding "System.map" gave me an error (i guess compiling kernels using emerge count as a compiled kernel...).
this is the error:

localhost josh # mv /usr/src/linux/System.map /boot/System.map-$(uname -r)
mv: cannot stat `/usr/src/linux/System.map': No such file or directory

so, the only way to fix this warning is to compile (and use) a new kernel? could i safely tell portage not to install new kernels? it seems like a newly emerged kernel is often a dependency for some other things, this is why i asked if i could prevent portage from installing/emerging new kernels. i also like using the vanilla kernels set up on my own

[variant]

he inadvertantly included part of annother command in the command you should run. the propper command is:

mv /usr/src/linux/System.map /boot/System.map

make sure /boot is mounted "mount /boot" before running that command or nothing will happen

[josolanes]

he inadvertantly included part of annother command in the command you should run. the propper command is:

mv /usr/src/linux/System.map /boot/System.map

make sure /boot is mounted "mount /boot" before running that command or nothing will happen

that gave me the exact same error. i'm starting to notice a trend though...look for "System.map" and put it in the right directory...so i did:

find / System.map

to see if it even exists...and to my dismay there is no System.map on my computer (atleast that the above command could find). what do i do now?

thanks a lot for your help!

[variant]

recompile your kernel or ignore the error, it is harmless.

[josolanes]

recompile your kernel or ignore the error, it is harmless.

ok...sounds good. i might upgrade my kernel when i recompile it (if i decide to even bother)

thanks a lot