On 2012-12-08 18:07 (GMT-0800) les composed:
On Sat, 2012-12-08 at 15:06 -0500, Felix Miata wrote:
Is this problem restricted to machine(s) only you use?
If yes, were Grub Legacy behavior and features adequate for your needs?
If yes, consider removing Grub2 and installing Grub Legacy using CPIO and/or MC and the instructions on http://orgs.man.ac.uk/documentation/grub/grub_3.html#SEC9. That way Yum won't try to remove or disturb it.
I don't install any bootloader during system installation when the only bootloader option presented is Grub2, but I don't have any systems that require features Grub Legacy lacks.
I certainly could do that, but what would happen then to updates?
Which updates? Grub2 won't get updated if it isn't installed. You'll need to update Grub's menu yourself at kernel update time. You can make that easier on yourself by maintaining /boot/vmlinuz-cur and /boot/vmlinuz-prv symlinks to the two most recent kernels and use the symlinks in Grub's menu. I have a boot partition I don't mount as boot, and keep a fully self-maintained Grub on it to use instead of all the Grubs installed to / partitions.
Once any Legacy Grub is installed and working properly, it _never_ needs to be updated to a newer version. Only the boot menu needs to be kept maintained to match the installed kernels and initrds. With the much more complex and still significantly evolving Grub2, that's not so.
Would the tools be clobbered with the grub2 stuff later?
Which tools? -- "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/ -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
