+++ mukund [linux-india] <03/01/02 11:01 +0530>:
> What is the role of /boot/system.map
> I can load kernel 2.4, when system.map is pointing toward kernel 2.2 map
> using lilo.
Everytime you compile a kernel, system.map is created to map the kernel
address locations of assorted variables and functions to symbolic names.
Something like you link a .o to an executable with gcc.
Every time you compile your kernel, this info changes (variable addresses
etc) so system map has to be updated.
So you might see stuff like
System.map does not match actual kernel
module <foo> could not be loaded because some versions do not match
on bootup, if your sytem map doesn't match.
The fix is simple - just change the system.map symlink to point to your
current kernel's system.map file (which should be there in /boot happen you
did a make install).
When a protection fault happens, klogd translates the addresses (total
gibberish effectively) to symbols, using the system.map - for easy debugging
basically - so you find out exactly what a kernel was doing when the error
occured. Progs like lsof also use the system.map file.
klogd looks for system.map in three places - in the order
/boot/System.map
/System.map
/usr/src/linux/System.map
-srs (all this googled out when I had this problem earlier ...)
--
Suresh Ramasubramanian <----> mallet <at> efn dot org
EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin
[Linux One Stanza Tip] From : <[EMAIL PROTECTED]>
LOST #035 -**< Sub : links console browser >**-
Links browser, supports frames and tables ...
For a reasonably good Console based browser visit here:
http://artax.karlin.mff.cuni.cz/~mikulas/links/
_______________________________________________
linux-india-help mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/linux-india-help
