2009/12/9 Stefan Seyfried
On Wed, 09 Dec 2009 10:58:05 -0600 Larry Finger
wrote: Now my system boots 3 different openSUSE distributions with multiple kernels in each, and I generate a new kernel on a daily basis. Keeping lilo current would be a big hassle.
No. You'd just chain two bootloaders together: one in the MBR that selects the distro to boot and the second in the root partition that then selects the kernel from the distribution. Ok, you'd need to add the newly compiled kernel to the config, but that's true for Grub, too.
And if you do it the best way, you don't have to change anything at
all. New kernel no problem, and only "tried and trusted" boot code
*NOT* new installs gets run. ( that's just reminded me to make sure
there's an option not to install any boot code in oS-11.3 after the
time wasting required to check it all in 11.2 )
There's better things to do in life, than moving through multiple boot
loaders and have in effect nested menu's of options. Then when you
have a boot issue, where do you start?
2009/12/9 Per Jessen
Rob OpenSuSE wrote:
If you run multiple distro-releases which you boot from a master spot, then not having the lilo map files is a big advantage.
I only run one distro - having multiple distros running in production is just hassle.
Well if you have have a production server, with a backed up copy of /boot directory, then you you'll have much more chance of booting from it, when you need to than with lilo(8). GRUB is reliable to in a sane configuration, and far more boring when you want to change something (and if it's a server boring is good). Rob -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org