On Tue, 1 Sep 2015 11:33, Carlos E. R. wrote:
On 2015-09-01 11:04, Felix Miata wrote:
greg.freemyer@ composed on 2015-08-31 20:56 (UTC-0400):
The bigger issue is who are the enthusiasts that will maintain grub, grub2, lilo, initrd, and of course the kernel.
Seems to me decade or older 32 bit CPUs ought to get along just fine without any "maintenance" on Grub Legacy, and for most need none of what Grub2 provides that Grub Legacy doesn't.
Well, yes, unnecessary things would have to be dropped, and keep only the easiest to maintain.
UEFI: no. There should not be UEFI/32 bit machines.
Apple laughts at you. They started using EFI on 32bit CPUs. They have even the ugly construct of 32bit EFI on 64bit CPU boards.
lilo, grub 1: no. Grub2 is easier to maintain (not as user, but as maintainer).
Did lilo (and syslinux) need any maintainance in the last 3 years? Can't remember that, I'd keep the packages, (mostly for the ones that HATE grub and grub2, to keep them silent, they know what they do by hand, no Yast2 support since 13.1 or even 12.3). But grub1, that is a beast. 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.
initrd? Keep dracut, I guess. Based in 13.2/tumbleweed.
Today dracut is mature enough for the most common cases, and for the cases where dracut does not work, even initrd has troubles. - Yamaban. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org