David McMillan wrote:
Donn Washburn wrote:
From the latest SuSE Online update of the kernel. Check in /var/log/boot.msg <- It is the first 4 lines
Inspecting /boot/System.map-2.6.11.4-21.7 Loaded 27512 symbols from /boot/System.map-2.6.11.4-21.7. Symbols match kernel version 2.6.11. <- NOTE No module symbols loaded - kernel modules not enabled.
Another reason to download and compile your own.
I wasn't sure what Donn meant here.
So, for we amateurs in the audience who barely know a kernel from a colonel, is there a moderately detailed, fairly concise tutorial around anywhere explaining the why, the when, and the how behind this particular part of linux use? And, most importantly, how to survive if/when something goes wrong?
Yesterday and on many other occasions I've posted replies saying how this can be done safely. You don't really want to damage your installation when messing with a new kernel by overwriting anything in /boot, a new kernel should always be considered as an experimental kernel to support some special bit of hardware or to see if a problem you experience is resolved by it. If you have problems with the new kernel, you should be able to simply reboot your working kernel and carry on as before. The name of the new kernel, initrd, System.map, etc. in /boot should be unique, you can start off right by adding a digit or letter to the EXTRAVERSION in the kernel Makefile so your new kernel will be e.g 2.6.11.4-21-7a or whatever you fancy. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks