From: Prarit Bhargava <prarit@redhat.com>
To: Colin Watson <cjwatson@ubuntu.com>
Cc: grub-devel@gnu.org
Subject: Re: [PATCH] Clarify "Press any key to continue..." message
Date: Thu, 03 Apr 2014 12:57:22 -0400 [thread overview]
Message-ID: <533D92F2.1000602@redhat.com> (raw)
In-Reply-To: <20140403165257.GU32733@riva.ucam.org>
On 04/03/2014 12:52 PM, Colin Watson wrote:
> On Thu, Apr 03, 2014 at 12:49:50PM -0400, Prarit Bhargava wrote:
>> On 04/03/2014 10:23 AM, Colin Watson wrote:
>>> When grub_wait_after_message says "Press any key to continue...", it
>>> really means that it will continue anyway after a short delay, but that
>>> you can press a key to skip the delay. Unfortunately, the delay is just
>>> long enough that in practice a number of users have time to see it,
>>> press a key, and then report a bug saying that their system won't boot
>>> without manual intervention, even though it would have booted just fine
>>> if they'd left it alone. Rephrase this message to make it clearer
>>> what's really happening.
>>
>> I have mixed feelings about changing this message since it is such a
>> well known message. OTOH, I've never really liked it myself.
>
> Surely nobody can really be depending on it; I don't see a problem with
> changing that kind of text, in and of itself.
Yeah ... but it is one of those things like the NMI dazed and confused message.
Everyone knows about it, everyone agrees it could be better, but no one wants
to change it because so much open documentation references it.
Try googling linux + "Press any key to continue" and you'll see what I mean.
But again, I've never really cared for the message so I'm favour of changing it ;)
>
>> Maybe a better idea is to do a timeout message
>>
>> Press any key for menu (boot will continue in 5 seconds) ...
>> Press any key for menu (boot will continue in 4 seconds) ...
>> ...
>> etc.
>>
>> ?
>
> It's not necessarily "for menu" - you get this for errors after a menu
> item has been selected too, and then it's just a delay before booting.
Hmm ... really? After a menu item has been selected? I've never done that before.
>
> Seems like a lot of effort. The actual delay is 2.5 seconds so a
> countdown would look jumpy at the end ...
>
Just do a countdown and change the delay to an even 3 seconds. Who is really
going to care about a 1/2 second?
P.
next prev parent reply other threads:[~2014-04-03 16:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 14:23 [PATCH] Clarify "Press any key to continue..." message Colin Watson
2014-04-03 16:49 ` Prarit Bhargava
2014-04-03 16:52 ` Colin Watson
2014-04-03 16:57 ` Prarit Bhargava [this message]
2014-04-03 17:11 ` Colin Watson
2014-04-03 17:15 ` Andrey Borzenkov
2014-04-07 17:25 ` Colin Watson
2014-07-23 7:44 ` Vladimir 'φ-coder/phcoder' Serbinenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=533D92F2.1000602@redhat.com \
--to=prarit@redhat.com \
--cc=cjwatson@ubuntu.com \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).