From: ludo@gnu.org (Ludovic Courtès)
To: Marius Bakke <mbakke@fastmail.com>
Cc: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>, 30312@debbugs.gnu.org
Subject: bug#30312: documentation: misleading EFI partitioning instructions
Date: Tue, 26 Jun 2018 22:14:09 +0200 [thread overview]
Message-ID: <87k1ql2tm6.fsf@gnu.org> (raw)
In-Reply-To: <87h8lpy3sg.fsf@fastmail.com> (Marius Bakke's message of "Tue, 26 Jun 2018 17:18:39 +0200")
Marius Bakke <mbakke@fastmail.com> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
[...]
>>> I'm not sure how to best resolve the first issue. I suppose we can
>>> mention that if unsure which GRUB to use, the user can test whether
>>> "/sys/firmware/efi" exists on the live image.
>>>
>>> We could also make it clearer when booting whether the installer is in
>>> "UEFI" mode or not.
>>
>> Maybe ‘guix system’ could warn, but I’m not sure how to do that in a
>> clean way.
>
> I was thinking a visual hint when booting the live USB, e.g. in the
> motd:
>
> (if (file-exists? "/sys/firmware/efi")
> "Welcome to the GuixSD installation image (UEFI mode)!".
> "Welcome to the GuixSD installation image!")
>
> I think Debian does something like this in the boot menu (IIRC).
The body is just plain static text, so I’m not sure how we could do
this. We’d need a bit of code to do that in /etc/profile or something.
Ideas?
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-06-26 20:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 19:01 bug#30312: documentation: misleading EFI partitioning instructions Ricardo Wurmus
2018-02-01 9:13 ` Gábor Boskovits
2018-02-01 11:01 ` Gábor Boskovits
2018-02-01 21:23 ` Joshua Branson
2018-02-01 22:19 ` Carlo Zancanaro
2018-06-26 8:12 ` Ludovic Courtès
2018-06-26 10:11 ` Marius Bakke
2018-06-26 13:55 ` Ludovic Courtès
2018-06-26 15:18 ` Marius Bakke
2018-06-26 20:14 ` Ludovic Courtès [this message]
2018-07-05 9:58 ` Ludovic Courtès
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=87k1ql2tm6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30312@debbugs.gnu.org \
--cc=mbakke@fastmail.com \
--cc=ricardo.wurmus@mdc-berlin.de \
/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).