unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: 30312@debbugs.gnu.org
Subject: bug#30312: documentation: misleading EFI partitioning instructions
Date: Tue, 26 Jun 2018 10:12:01 +0200	[thread overview]
Message-ID: <871scu6k6m.fsf@gnu.org> (raw)
In-Reply-To: <idjlggd4ztn.fsf@bimsb-sys02.mdc-berlin.net> (Ricardo Wurmus's message of "Wed, 31 Jan 2018 20:01:56 +0100")

Hello gentlefolks!

Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:

> First, this sounds like it’s up to the user to pick either EFI-based
> GRUB or BIOS-based GRUB.  It is not clear that this is determined by
> whether the machine has a {BIOS, EFI in legacy mode} or EFI.  It’s
> really not much of a choice.
>
> Second, the “parted” command operates on the first partition (“1”), yet
> for the second command the second partition (“/dev/sda2”) is used.  It’s
> better to be consistent here, i.e. to change “set 1 esp on” to “set 2
> esp on” and to state that this would modify “/dev/sda2”.
>
> Finally, it is not clear where the efi partition should be mounted.
> Should it be /mnt/boot/efi?  If so, should the configuration file
> specify “/mnt/boot/efi” as the target?  Or should it be “/boot/efi”?
>
> An example would be useful here.

It’d be nice to fix this before the release.  Anyone could take a look
to address these issues?

Thanks,
Ludo’.

  parent reply	other threads:[~2018-06-26  8:13 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 [this message]
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
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=871scu6k6m.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=30312@debbugs.gnu.org \
    --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).