On Thu, May 31, 2018 at 11:31 AM, Hans de Goede <hdegoede@xxxxxxxxxx> wrote: > Hi, > > On 31-05-18 15:08, Chris Adams wrote: >> >> Once upon a time, Hans de Goede <hdegoede@xxxxxxxxxx> 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 > system. I was going to bring up one sort of niche use-case, of installing a -debug kernel (either while working on the kernel or helping to debug an issue that the kernel developer cannot reproduce), since debug kernels end up a lower priority and wouldn't normally be the default selection.. but a reboot-grubmenu command would totally cover that use-case. Side note, android's 'reboot' cmd can take an argument, like 'reboot fastboot' or 'reboot recovery'.. that might be one of the few features from android worth copying ;-) BR, -R > 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. > > 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/P6KOCFBMV4MZF2R4RQKSX4VUO7QD6RWN/ _______________________________________________ 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/46GZ2YY54RCD4NZJO25VUNLQYC5REDSF/
