unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Joshua Branson <jbranso@fastmail.com>
To: 30312@debbugs.gnu.org
Subject: bug#30312: documentation: misleading EFI partitioning instructions
Date: Thu, 01 Feb 2018 13:23:12 -0800	[thread overview]
Message-ID: <1517520192.3013052.1256470944.089A5312@webmail.messagingengine.com> (raw)
In-Reply-To: <CAE4v=pieOc-B38NPYeM-vzgfQbOAMaxKryAc2_T1hAGBbf+b+g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2670 bytes --]

By no means am I a developer, but that sounds like a good idea.


On Thu, Feb 1, 2018, at 3:01 AM, Gábor Boskovits wrote:
> 2018-02-01 10:13 GMT+01:00 Gábor Boskovits <boskovits@gmail.com>:
>> 2018-01-31 20:01 GMT+01:00 Ricardo Wurmus <ricardo.wurmus@mdc-
>> berlin.de>:>>> The manual section “Preparing for Installation: Disk
>>> Partitioning” says>>>  this:
>>> 
>>>  --8<---------------cut here---------------start------------->8---
>>>     If your disk uses the GUID Partition Table (GPT) format and you
>>>     plan>>>  to install BIOS-based GRUB (which is the default), make sure a
>>>  BIOS Boot>>>  Partition is available (*note (grub)BIOS installation::).
>>> 
>>>     If you instead wish to use EFI-based GRUB, a FAT32 “EFI System
>>>  Partition” (ESP) is required.  This partition should be mounted at>>>  ‘/boot/efi’ and must have the ‘esp’ flag set.  E.g., for ‘parted’:>>> 
>>>       parted /dev/sda set 1 esp on
>>> 
>>>     Once you are done partitioning the target hard disk drive, you
>>>     have>>>  to create a file system on the relevant partition(s)(1).  For
>>>  the ESP,>>>  if you have one and assuming it is ‘/dev/sda2’, run:
>>> 
>>>       mkfs.fat -F32 /dev/sda2
>>>  --8<---------------cut here---------------end--------------->8---
>>> 
>>>  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.
>>> 
>> I agree an example would be nice.
>> I will have a look at this when I have time.
>> I guess I had done something similar.
>> 
> I've just looked around and found that we have ovmf in our repository.> It would be nice if we could create a system test and use an ovmf qemu
> to test installation.> Once we have that we could get the documentation consistent with a
> working testcase.> WDYT? 
>>  
>> 
>>> --
>>>  Ricardo
>>> 
>>> 
>> 


[-- Attachment #2: Type: text/html, Size: 6397 bytes --]

  reply	other threads:[~2018-02-01 21:48 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 [this message]
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
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=1517520192.3013052.1256470944.089A5312@webmail.messagingengine.com \
    --to=jbranso@fastmail.com \
    --cc=30312@debbugs.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.
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).