On Thu, May 31, 2018 at 12:09:45PM -0500, Chris Adams wrote:
Once upon a time, Hans de Goede <hdegoede(a)redhat.com> said:
> On 31-05-18 15:08, Chris Adams wrote:
> >Once upon a time, Hans de Goede <hdegoede(a)redhat.com> said:
> >>And for F30, single OS 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
> >If I know I want the menu (say I need to boot single-user to fix
> >something), how would I do that in this setup?
> Hopefully what ever you want to fix will count as a "failed boot"
> if it requires single user mode.
Hmm... not really. For example (just off the top of my head): lost root
password. Without it, you won't be able to set any "next boot is
special" option, so resetting root's password would now require rescue
I'd say I'm against this part of your proposal. I understand the
reasoning, but it just seems like too much restriction to shave off a
small amount of time. You mentioned it "could take several seconds" for
EFI to initialize USB, but what is the normal time, for a typical
desktop or notebook with just a keyboard and mouse attached?
I agree. Another use case is that failed graphics initialization may
not count as "failed boot".