On 2014-07-18 09:17 (GMT-0700) Thomas Taylor composed:
During the initial installation of OS 13.2 (snapshot
20140630 x86_64) when
choosing boot options legacy grub is not offered, only grub2. Yet legacy grub
is offered as a software package option.
Why is installation of legacy grub offered if it
can't be used as the boot
I asked on the more pointed list 6 days ago:
No responses as yet.
Is it finally time that I'm forced to change boot
loaders and to learn a new
method? I like legacy grub as it is easy to modify menu.lst but grub.cnf
appears to be much more complex.
Upstream wants no one modifying grub.conf manually, and for good reason,
since it is so much more complicated than menu.lst, and error prone manually
If you know how to use the grub> (legacy) shell, the only Grub config files
needed are device.map and menu.lst, and if you know the shell, you can get by
without any menu.lst any time need be. If your system is already multiboot,
then you need no bootloader installed at installation time, if ever. That's
how I've been doing Fedora installations since it reduced its choices to
Grub2 and no bootloader. Once I have Fedora installed, I install openSUSE's
Grub Legacy on it, mainly for chainloading to whenever I want to use a
non-default kernel. Keeping a master bootloader configured for all kernels on
all installations is an unnecessary, complicated, sticky wicket obviated by
having a simple bootloader configured on each / for any optional kernels.
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org