Brad Shelton wrote:
Personally, I would be careful doing this next step. I would either do a 'make zlilo', which copies /vmlinuz to /vmlinuz.old and makes an additional entry in your /etc/lilo.conf file which gives you the option of booting the old kernel in case the new one doesn't work, or I would 'cp /vmlinuz /vmlinuz.old' and make the entry manually in /etc/lilo.conf. If you don't and the new kernel won't boot for some reason, you're screwed.
Brad has a point. I have a vfat partition "/dos" which I use to share files between linux and windows, and I always: "cp /vmlinuz /dos/vmlinuz", that way if there is a problem with the new kernel I can boot my old kernel with loadlin and bail myself out. You are UNLIKELY to ever have problems with a non-development kernel, but it's always wise to be cautious. -- ==================================================================== Michael Lankton <A HREF="http://tasteslikechicken.ml.org"><A HREF="http://tasteslikechicken.ml.org</A">http://tasteslikechicken.ml.org</A</A>> ==================================================================== - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e