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?
Stephen Boulet wrote:
> I *think* that the link the system.map points to is updated when you run make
> install (somewhat automated kernel install). Check the timestamp of the files
> in /boot, and check to see if the link itself is pointing to the right one.
>
> -- Stephen
>
> On Sat, 11 Mar 2000, you wrote:
> > There are two files in the /boot directory that I don't understand:
> >
> > System.map
> >
> > module-info
> >
> > Both are typcially symbolic links to other files. The System.map file is
> > also in the /usr/src/linux file and is generated anew during the kernel
> > compilation process but I am not certain which make xxx function
> > generates it (where xxx= dep, clean, bzImage, modules, or
> > modules_install) since I usually compile with all of the commands in a
> > single line with the && shell function.
> >
> > I would be most grateful for elucidation on the subject since I have not
> > been able to find anything in the kernel HOWTO or in any of the many
> > linux books that I have.
> >
> > Thanks
> >
> > Tom
