Re: Hiding the grub menu by default on single OS installs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On 01-06-18 20:38, Andrew Lutomirski wrote:
On Jun 1, 2018, at 1:04 AM, Hans de Goede <hdegoede@xxxxxxxxxx> wrote:

Hi All,

First of all I want to thank everyone for their input.

I also want to make clear that the hide the menu +
not listening for a keypress at all (aka fastboot) is a
Fedora 30 thing, quoting myself:

"For F29, single OS Fedora Workstation install we get:

1) grub menu hidden by default with a 1 second timeout to press ESC
or F8 to show it

As discussed, this isn’t so great. Can we at least let users hold down
a key rather than having to press it at the correct magic time?

Because detecting modifiers with UEFI is iffy and with
serial consoles is outright impossible.

2) grub menu shown with 5 sec timeout after a failed boot

For F30, single OS Fedora Workstation install install we get:

1) grub menu not shown, 0 second timeout, no way to get to the menu
2) grub menu shown with 5 sec timeout after a failed boot"


I think this is a severe regression.  There are multiple use cases
that you’re breaking:

1. Nothing failed per se, but I want to test a boot option.  I
shouldn’t need to reconfigure grub.

There will be a commandline tool to request to show grub the next
boot. Elsewhere in the thread someone mentioned that windows now
shows it boot menu when doing shift + reboot, I think it would be
nice to do something similar in GNOME.

2. The system booted successfully but is unusable (due to a graphical
glitch caused by a kernel regression, a lost driver due to a dracut
issue, or maybe some filesystem issue causing login to fail or the
session post-login to be unusable).  It would be fixable by booting an
older kernel or entering an appropriate recovery mode, but if the menu
is entirely gone, then it can’t.
>
> 3. The boot failed outright and the “failed boot” logic is busted.

2 and 3 really are the same.

As mentioned in the part of my mail which has been snipped in
the reply you are replying to, the plan is to start a systemd timer
as part of the user session which considers the boot successful
if the user session stays alive for 2 minutes.

So if you reboot or force-poweroff within 2 minutes next boot
you will get the boot menu.

I think this is asking for far more trouble than the benefit is worth.
I’m not on FESCo, but if I were, I would definitely vote -1.

Please at least do the bare minimum and teach grub to notice that some
key is held down and show the menu in response.

See above why modifiers cannot work.

Regards,

Hans
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/FE2LRGIORYJU4QRTSHFVSMDHPL7UR7QG/




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux