On Sat, Jun 29, 2019 at 1:05 AM Nicolas Mailhot via devel <devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > Le vendredi 28 juin 2019 à 18:49 -0600, Chris Murphy a écrit : > > I think that's completely out of scope. It's inappropriate to wait 10 > > months let alone 10 years to resolve this problem. And it's an overly > > complicated solution. > > It's not an overcomplicated solution it's just putting a single stable > unchanging installation command in front of whatever anaconda does. > Which grubby was not since it was grub-specific with lots of options. grubby isn't GRUB specific. It supports LILO, ELILO, SILO, ZIPL, extlinux, GRUB legacy, GRUB2, yaboot, and something else I'm forgetting no doubt. This also seems applicable https://xkcd.com/927/ > Not making the effort to put this single command in place, is the > reason why Fedora boot problems in 2019, are the same than RHL boot > problems in 2000: a. Near as I can tell, the only system under discussion, x86 + BIOS + multiboot, means exactly one bootloader: BIOS GRUB. That's the only bootloader Fedora supports in that configuration. b. Fedora only narrowly supports multiboot: Fedora + Windows, and Fedora + macOS. As in, only the dual boot variety, and not any Linux distros. Not even Fedora + Fedora is supported. By that I mean, there is no release criteria that forms a basis for blocking the release if something related to creating such a setup during installation is found to be broken. I just don't see how a single command to rule them all solves a single problem. It's like playing musical chairs, except no seat has been removed. > 1. no one knows exactly what to call to reinstall the bootloader except > bootloader people (it changes and is badly documented), Fedora x86 BIOS, it's been 'grub2-install' since circa Fedora 14. And on UEFI since early days it's reinstall shim and grub packages, also hasn't changed. > > 2. therefore no one can test the result on the scale needed for the > variety of hardware out there > > 3. when someone hits a bootloader problem, and tries to fix his system > with whatever lies on the internet (because the documentation is not > here, and the documentation is needed, because the actual commands to > type change), it's never exactly what bootloader people think he should > do, so the result is invalid (positive or negative), and not used to > improve the way Fedora does things But in effect you're proposing the inevitable day when the user still invokes grub2-install, and the Fedora oracles still say "yeah that's deprecated on Fedora, you ran the wrong command, that's why your system is now hosed" By the way, bootctl is already taken by systemd-boot. -- Chris Murphy _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
