Originally Posted by onebuck
Read the referenced links and then come back. You may not need it but it would be nice to have it when you do; Just one of many reasons that justify and provide a means to get information at times to diagnose.
Your system to do as you like but a generic statement as you put it. Not on my system!
Did you read my post?
I was replying to this:
Originally Posted by T3slider
The only important symlink there is System.map --> System.map-generic-smp-220.127.116.11-smp, and I'm not 100% sure whether that's needed either.
What I said with this:
Originally Posted by chrisretusn
You don't need any of those symlinks IF you are specifying the exact kernel to boot from (e.g., vmlinuz-generic-smp-18.104.22.168-smp) in lilo.
Using symlinks is standard practice and make things simple.
Exactly were in my post did I say that System.map was not
One could also name the System.map file System.map-22.214.171.124-smp.
At any rate a Linux system should run just fine with out System.map symlinked. I did not advocate doing so I simply said the symlink is not needed. Please feel free to give me some specifics in which the symlink is needed to run Linux, not debug it.
Did you know in Slackware klogd does not use System.map, it hasn't for quite some time. From rc.syslog:
echo "/usr/sbin/klogd -c 3 -x"
# '-c 3' = display level 'error' or higher messages on console
# '-x' = turn off broken EIP translation
/usr/sbin/klogd -c 3 -x
The 2.6 kernel can decode most kernel oopses and produces decent dumps on it's own with out the use of System.map. Both the generic and huge kernels are built with CONFIG_KALLSYMS.
In the for what it is work department; I do symlink System.map to match my kernel.
Just for kicks, I am running another Slackware box without the kernel System.map linked, renamed to System.map or using the 'uname -r' suffix. I am keeping the standard Slackware names.