Hans de Goede wrote: > On 31-05-18 15:20, Robert Marcano wrote: > > What is the definition of a successful boot? I ask because a machine could > > boot perfectly, and when you try to interact with it on the login screen, > > bugs on the display driver can change the screen to garbage (I have seen > > this kind on bug long time ago), or lockup. So, the user will be unable to > > activate any kind of restart with menu enabled in order to try an older > > kernel, or boot to rescue mode. > > > > I think instead of only detecting a successful boot, a machine that wasn't > > properly shutdown should enable the menu > > A broken install may still shutdown properly after the using pressing the > power-button and/or > trying ctrl+alt+del. > > But this is an interesting suggestion, I think we should track both > separately, > so successful shutdown and successful boot and show the menu if either one is > not true. That should make the chance of not being able to get the menu a lot > smaller.
This is starting to sound rather complex, and complex code is prone to bugs. I want my bootloader as simple and straightforward as possible to minimize the risk of problems. I would hate to run into some bug that renders the system unusable, and then find that I can't do anything about it because a separate bug causes Grub to not display the boot menu. Björn Persson
pgpn63RGL_xaV.pgp
Description: OpenPGP digital signatur
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org/message/3BDC5QQWQQGR3VIIXJO6TNXUZF7FXUSU/
