Hi,
please see the klogd(8) manual page for info about the System.map file.
On Mar 12 Tom Berkley wrote:
> No, the System.map in boot in not affected by a kernel compilation. The
> System.map in /usr/src/linux ( or wherever you installed the source) is updated.
> I'm thinking that the System.map in /usr/src/linux needs to be copied to /boot
> with a unique id and then point the /boot/System.map to that file before
> running lilo and rebooting (assuming the corresponding kernel is in the /boot
> directory along with it) But there is something that does not seem correct about
> this because then how would you boot to another kernel without editing the link,
> rerunning lilo and then rebooting. Just does not compute.
>
> Does the kernel find the correct System.map file when it boots?
>
If you use more than one kernel, then copy /usr/src/linux/System.map
to /boot/System.map-`uname -r` and start klogd with the `-k' switch
at boot time, i.e.
klogd -k /boot/System.map-`uname -r` from /etc/rc.d/init.d/syslog.
Rene
--
UNIX was never designed to keep people from doing stupid things, because
that policy would also keep them from doing clever things. (Doug Gwyn)
