On 17 Aug 2001 10:35:49 -0500, [EMAIL PROTECTED] wrote: > > Hi, > > Yesterday I had an interesting conversation with someone on the #debian > IRC channel re: compiling a custom kernel. He urged me to add the > following lines to my /etc/lilo.conf file: > > image=/boot/vmlinuz-2.2.17 > label=prev2217 > > ... and make sure I could boot the system from this choice. It worked > fine. > > Now I am slogging through the documentation on kernel-package, prepping to > compile 2.4.8. To make matters short, I guess I'd like to know: given this > [working] addition to /etc/lilo.conf, should I be relatively safe to go > ahead and futz? Of course I'll keep reading and prep best I can, but > experience tells me I usually flub *something* and I'd like to make sure I > can get back to trusty my 2.2.17 before going much further.
Installing a deb of your custom kenel-package compiled kernel should be fine. Assuming you don't forget to compile in your root disk access drivers (scsi or ide) like I've done more times that I'd care to admit. If you're really worried make a bootfloppy from the running 2.2.17 kernel with mkboot after reading the man pages. The deb package should automagically update your lilo.conf for you. --mike
