On Mon, Mar 28, 2016 at 11:44 PM, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
Отправлено с iPhone
29 марта 2016 г., в 7:09, Chris Murphy <lists@colorremedies.com> написал(а):
On Mon, Mar 28, 2016 at 9:24 PM, Andrei Borzenkov <arvidjaar@gmail.com> wrote: 28.03.2016 07:54, Chris Murphy пишет:
Long version: Basically the distros have a bunch of mutually incompatible forks of upstream GRUB.
How it is relevant in this case at all?
It's the superset position, the ultimate cause for all bootloading madness on Linux. It's not the user's fault they're so often confused about something that should be so basic and reliable. The GRUB2 multiboot experience handed to us by distros is basically crap and it's not really possible to overstate that.
This is marginally less crap with upstream GRUB. But it's actually nearly pleasant with systemd-boot (gummiboot) and rEFInd. So it's not
So rEFInd or systemd-boot will ignore file signature and allow you to load and launch anything you through at them? Otherwise please explain how using different boot loader would change anything here.
My recommendation is the same as when I first posted. Use the firmware's built-in boot manager. It solves all of these problems, the user doesn't have to get wrapped up in bootloader esoterics and workarounds. -- Chris Murphy -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org