Yamaban composed on 2015-09-01 12:58 (UTC+0200):
But grub1, that is a beast.
How so? I committed http://www.gnu.org/software/grub/manual/legacy/grub.html#Installing-GRUB-nat... to memory many years ago. It and a mcedit are all I need to make and keep an installation bootable - no need for any scripts, no need for chrooting or man pages to explain how to get any Grub2 script to do what is so simple to do with the Grub Legacy shell. KISS at its finest, easy to fix in those rare cases where it gets broken by some renegade installer or script. Whenever I install Fedora or openSUSE post-13.1, I choose install no bootloader at installation time. Then I install openSUSE 13.1's Grub Legacy in Fedoras, and zypper in grub in openSUSE. Multiboot life is blissful, without any of the Grub2 trouble I read about in forums and mailing lists.
Is there a fully working tool (cli, maybe even yast2 readonly) that takes a grub1-config and build a valid (as in: yast2 and grub2 works with it) grub2-config?
If yes, I'd vote for dropping grub1 and trusted-grub1 like a rotted egg.
How can Grub Legacy be hard to "maintain"? V2.03 now in TW repos had only had 5 patches post-13.1, possibly[1] all of which appear to this non-programmer to be build config/build dep related. [1] whether this was a build config/dep issue or not I cannot tell: https://bugzilla.opensuse.org/show_bug.cgi?id=918028 -- "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@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org