On 06/06/2018 03:04 AM, Dominik 'Rathann' Mierzejewski wrote:
On Friday, 01 June 2018 at 12:53, Hans de Goede wrote:
> On 01-06-18 11:54, Tomas Kovar wrote:
>> Hi all,
>> I have two suggestions:
>> - on UEFI systems, would it be possible to use an EFI variable to force grub
menu? That way, it would be possible to enter the menu from UEFI boot loader or shell,
even if the system itself is in non-working state or on read-only device.
> That is a good idea I've added looking into this to my TODO list.
What about UEFI systems where there's no way to get into EFI shell
because firmware is deliberately broken by the vendor to prevent
booting anything apart from Windows? I managed to get Fedora booting
with SecureBoot enabled on my system only by manually setting the
name of its boot entry to "Windows Boot Manager". There's no option
to boot anything else because any BootNext/BootOrder options set
with efibootmgr get ignored. I'm sure my machine is not an exception
in this regard, so you cannot rely on users being able to do anything
before GRUB comes up.
Disabling the GRUB menu and shortening timeouts is a bad idea in my
opinion. You don't boot so often these days and when you need to
access the GRUB menu, you usually do because something is broken and
you don't want to poke around the internet to find out how to do that
in Fedora because you might even have no internet access. There needs
to be a clear hint on the screen how to access the menu visible long
enough for the user to read it.
I especially think that if you're going to show *anything*, it might as
well be the menu itself.