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

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

 



On 06/01/2018 02:39 PM, 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?
>
>> 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.
>
> 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.
>
> 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.
I have to agree here. Personally, I would keep the menu as is.
> _______________________________________________
> 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/RJIG7KP6L3S2PVH5JJNWXYFLA5OEQ6L6/


-- 
Roger Wells, P.E.
leidos
221 Third St
Newport, RI 02840
401-847-4210 (voice)
401-849-1585 (fax)
roger.k.wells@xxxxxxxxxx

_______________________________________________
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/TLBWWMZGJNJYEEVJANWYQ327W6X7YWB7/




[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