Thank you James and Carlos for the LILO insights. I think I'll stick with LILO for now (if it ain't broke, don't fix it!) Thanks again, Matt ---------- Original Message ---------------------------------- From: "James D. Parra" <Jamesp@MusicReports.com> Date: Wed, 2 Nov 2005 11:30:23 -0800

...

That you need to run 'lilo' after doing any change to the bootloader configuration or a kernel update or change. Grub doesn't need that.

...

Grub can read directly from the filesystem, so it can read the menu and other files directly during boot. On the other hand, lilo can not do that, it needs a map to find those things it needs being compiled before hand (by running the 'lilo' command).

Just to concur with Carlos, after any kernel upgrade, you'll need to run "#/sbin/lilo" to update Lilo's boot selection. There is plenty of documentation for lilo and it is easy to update and modify. It may lack a few of the functions that Grub supports, but it works well enough. You won't be disappointed. Besides, after you make any changes you need or want, you won't need to tend to it again.

~James

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com