From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1WVkxa-0000Id-OS for mharc-grub-devel@gnu.org; Thu, 03 Apr 2014 12:57:50 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51227) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WVkxT-0008VA-13 for grub-devel@gnu.org; Thu, 03 Apr 2014 12:57:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WVkxA-0008W0-5U for grub-devel@gnu.org; Thu, 03 Apr 2014 12:57:42 -0400 Received: from mx1.redhat.com ([209.132.183.28]:8624) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WVkx9-0008Vm-R3 for grub-devel@gnu.org; Thu, 03 Apr 2014 12:57:24 -0400 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s33GvMP7007569 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 3 Apr 2014 12:57:23 -0400 Received: from prarit-guest.khw.lab.eng.bos.redhat.com (prarit-guest.khw.lab.eng.bos.redhat.com [10.16.186.145]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s33GvM5J032338; Thu, 3 Apr 2014 12:57:22 -0400 Message-ID: <533D92F2.1000602@redhat.com> Date: Thu, 03 Apr 2014 12:57:22 -0400 From: Prarit Bhargava User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131028 Thunderbird/17.0.10 MIME-Version: 1.0 To: Colin Watson Subject: Re: [PATCH] Clarify "Press any key to continue..." message References: <20140403142317.GT32733@riva.ucam.org> <533D912E.6060102@redhat.com> <20140403165257.GU32733@riva.ucam.org> In-Reply-To: <20140403165257.GU32733@riva.ucam.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.68 on 10.5.11.23 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 209.132.183.28 Cc: grub-devel@gnu.org X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2014 16:57:49 -0000 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.