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.
I can and certainly will add a commandline utility to force showing
the menu on the next boot, but that assumes a somewhat working
I guess the plan is to have a few daemons which are considered
critical (if enabled) say sshd and gdm and if any of them don't
start, consider the boot failed. This also means that if you
ctrl+alt+del early on, causing the system to reboot without
ever starting those that will also give you the grub menu.
Note that this is exactly why this is a F30 thing, to give us
a chance to figure out how exactly to detect a failed boot.
Also I would like to note that Windows has been doing more or
less the same since Vista and it does not seem to cause any
problems for Windows.