John Lamb wrote:
Martin wrote:
Ken, what should I do now to make sure they are
around? I guess at this point they are gone, correct? Thx, Martin
Not necessarily. The kernel modules get installed in /lib/modules/2.6.x where x is the version number. So if you are compiling a kernel with a different version number, you won't have overwritten the old modules and should can reboot with the old kernel.
If you look in the kernel Makefile, the fourth line reads
EXTRAVERSION =
You can change this to something else like
EXTRAVERSION = -xyz
Then the kernel modules will all get put in /lib/modules/2.6.x-xyz and its extremely unlikley that you'll ever get anything to conflict with them. You can even do this now and repeat the make bzImage and make modules_install steps.
It is now possible to compile kernels, even with the same version numbers, that won't conflict with each other. So you don't need to move the old kernel and therefore can guarantee you have something that will still boot.
This is exactly what I do, so you always have a fallback. You don't have to call the new kernel "vmlinuz", you can call it "strawberry" or "2.6.8-241" or whatever takes your fancy, as long as menu.lst contains an entry for it. 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 for all Computing Tasks