From: Mark H Weaver <mhw@netris.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Vagrant Cascadian <vagrant@debian.org>, 31159@debbugs.gnu.org
Subject: bug#31159: Reverse order for old grub.cfg entries
Date: Wed, 18 Apr 2018 15:23:19 -0400 [thread overview]
Message-ID: <87bmegiajc.fsf@netris.org> (raw)
In-Reply-To: <87604oy5j7.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Wed, 18 Apr 2018 16:04:44 +0200")
Hi Ludovic,
ludo@gnu.org (Ludovic Courtès) writes:
> I agree with you. As long as the entry labels clearly show which one is
> the most recent, that sounds good.
>
> However! On headless machines, we’d rather make sure users know about
> this change. On our Libreboot “bayfront” server, GRUB for some reason
> fails to display anything, and on several occasions we’ve had to blindly
> select an older generation. Hopefully this is an unusual situation ;-),
> but it could happen on ARM boards as well.
Do you have an idea of how to make sure that users know about it?
Mark
next prev parent reply other threads:[~2018-04-18 19:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r2lsji3l.fsf@lassieur.org>
2018-04-15 3:20 ` bug#31159: Reverse order for old grub.cfg entries Vagrant Cascadian
2018-04-15 17:22 ` Joshua Branson
2018-04-16 14:33 ` Mark H Weaver
2018-04-17 8:16 ` Mathieu Othacehe
2018-04-17 18:18 ` Mark H Weaver
2018-04-18 14:04 ` Ludovic Courtès
2018-04-18 19:23 ` Mark H Weaver [this message]
2018-04-18 20:14 ` Ludovic Courtès
2018-04-19 15:21 ` Mathieu Othacehe
2018-04-23 15:16 ` Ludovic Courtès
[not found] ` <handler.31159.C.152775849827440.notifdonectrl.0@debbugs.gnu.org>
2018-05-31 22:07 ` bug#31159: #31159: " Vagrant Cascadian
2018-06-01 2:18 ` Mark H Weaver
2018-06-01 7:46 ` Mathieu Othacehe
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bmegiajc.fsf@netris.org \
--to=mhw@netris.org \
--cc=31159@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=vagrant@debian.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).