/boot/System.map not parseable
During startup /shutdown and change of run levels
A message which says /boot/Sytem.map not parseable is always displayed . What could be the reason and how can i solve it . (This happens in RHL 6.0 ) |
Do you actually have problems, or just see the message and want it to go away?
Did you mess with /boot/System.map? In my distros it's usually a symlink to a longer named System.map file, like System.map-ide-2.4.18 would be the full name. So maybe it is a symlink and is now pointing to nothing, or the wrong file, or something similar to that. Type 'ls -l /boot' in a terminal to see if it is a symlink, and what it's pointing to if it is. Find out if the file exists. If you are still having problems, or my instructions aren't clear, you can post the output of 'ls -l /boot' here to see if anyone can help. Cool |
Thanks for the help . i 'll check that out . The sustem seems to work but i do wish not to see my message every now and then
|
If you changed your kernels at some point, you probably didn't put the system.map file for it in the /boot directory.
I think the system.map file is only there to give you better error messages anyway, but I could be wrong. |
wartstew, actually I believe it's a "map" file to the modules, /lib/modules/x.x.x
I will poke around and see if I can find a reliable source for info on what the file does. Cool |
Ok, not necessarily /. but some info nonetheless, I will see what else I can find.
http://www.dirac.org/linux/systemmap.html |
For a good overview what System.map is take a look at http://www.dirac.org/linux/systemmap.html
|
Hey, huh huh huh ;)
|
All times are GMT -5. The time now is 02:01 PM. |