From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joshua Branson Subject: bug#30312: documentation: misleading EFI partitioning instructions Date: Thu, 01 Feb 2018 13:23:12 -0800 Message-ID: <1517520192.3013052.1256470944.089A5312@webmail.messagingengine.com> References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="_----------=_151752019230130522" Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:43554) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ehMhJ-0007jk-FE for bug-guix@gnu.org; Thu, 01 Feb 2018 16:48:15 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ehMgF-00076f-Cf for bug-guix@gnu.org; Thu, 01 Feb 2018 16:47:09 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:44976) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ehMgE-00075f-Nj for bug-guix@gnu.org; Thu, 01 Feb 2018 16:46:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ehMgE-0001Ig-5T for bug-guix@gnu.org; Thu, 01 Feb 2018 16:46:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52139) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ehMLF-0004iL-DX for bug-guix@gnu.org; Thu, 01 Feb 2018 16:28:21 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ehMKB-0005dP-B1 for bug-guix@gnu.org; Thu, 01 Feb 2018 16:24:21 -0500 Received: from out3-smtp.messagingengine.com ([66.111.4.27]:43429) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ehMKA-0005c4-TN for bug-guix@gnu.org; Thu, 01 Feb 2018 16:23:15 -0500 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 0062120BF6 for ; Thu, 1 Feb 2018 16:23:13 -0500 (EST) In-Reply-To: List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: 30312@debbugs.gnu.org This is a multi-part message in MIME format. --_----------=_151752019230130522 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" By no means am I a developer, but that sounds like a good idea. On Thu, Feb 1, 2018, at 3:01 AM, G=C3=A1bor Boskovits wrote: > 2018-02-01 10:13 GMT+01:00 G=C3=A1bor Boskovits : >> 2018-01-31 20:01 GMT+01:00 Ricardo Wurmus > berlin.de>:>>> The manual section =E2=80=9CPreparing for Installation: D= isk >>> Partitioning=E2=80=9D says>>> this: >>>=20 >>> --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 su= re a >>> BIOS Boot>>> Partition is available (*note (grub)BIOS installation::). >>>=20 >>> If you instead wish to use EFI-based GRUB, a FAT32 =E2=80=9CEFI Sys= tem >>> Partition=E2=80=9D (ESP) is required. This partition should be mounte= d at>>> =E2=80=98/boot/efi=E2=80=99 and must have the =E2=80=98esp=E2=80= =99 flag set. E.g., for =E2=80=98parted=E2=80=99:>>>=20 >>> parted /dev/sda set 1 esp on >>>=20 >>> 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 =E2=80=98/dev/sda2=E2= =80=99, run: >>>=20 >>> mkfs.fat -F32 /dev/sda2 >>> --8<---------------cut here---------------end--------------->8--- >>>=20 >>> First, this sounds like it=E2=80=99s 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=E2=80=99s>>> really not much of a choice. >>>=20 >>> Second, the =E2=80=9Cparted=E2=80=9D command operates on the first par= tition >>> (=E2=80=9C1=E2=80=9D), yet>>> for the second command the second parti= tion (=E2=80=9C/dev/sda2=E2=80=9D) is >>> used. It=E2=80=99s>>> better to be consistent here, i.e. to change = =E2=80=9Cset 1 esp on=E2=80=9D to >>> =E2=80=9Cset 2>>> esp on=E2=80=9D and to state that this would modify= =E2=80=9C/dev/sda2=E2=80=9D. >>>=20 >>> 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 =E2=80=9C/mnt/boot/efi=E2=80=9D as the target? Or should it be >>> =E2=80=9C/boot/efi=E2=80=9D?>>>=20 >>> An example would be useful here. >>>=20 >> 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. >>=20 > I've just looked around and found that we have ovmf in our repository.> I= t 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 c= onsistent with a > working testcase.> WDYT?=20 >>=20=20 >>=20 >>> -- >>> Ricardo >>>=20 >>>=20 >>=20 --_----------=_151752019230130522 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8"
By no means am I a developer, but that sounds like a good idea.<= br>


On Thu, Feb 1, 2018, at 3:01 AM, G=C3=A1bor Boskovits wrote:
2018-02-01 10:13 GMT+01:00 G=C3=A1bor Boskovits <boskovits@gmail.com>= :
2018-= 01-31 20:01 GMT+01:00 Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>= :
The manual section =E2=80=9CPreparing for Installation: Disk Partitioning= =E2=80=9D says
this:

--8<---------------cut here---------------start-------------&= gt;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 B= oot
Partition is available (*note (grub)BIOS installation::).

   If you instead wish to use EFI-based GRUB, a FAT32 =E2= =80=9CEFI System
Partition=E2=80=9D (ESP) is required.  This partition should be = mounted at
=E2=80=98/boot/efi=E2=80=99 and must have the =E2=80=98esp=E2=80=99 f= lag set.  E.g., for =E2=80=98parted=E2=80=99:

     parted /dev/sda set 1 esp on

   Once you are done partitioning the target hard disk driv= e, you have
to create a file system on the relevant partition(s)(1).  For th= e ESP,
if you have one and assuming it is =E2=80=98/dev/sda2=E2=80=99, run:<= br>

     mkfs.fat -F32 /dev/sda2
--8<---------------cut here---------------end---------------&= gt;8---

First, this sounds like it=E2=80=99s up to the user to pick either EF= I-based
GRUB or BIOS-based GRUB.  It is not clear that this is determine= d by
whether the machine has a {BIOS, EFI in legacy mode} or EFI.  It= =E2=80=99s
really not much of a choice.

Second, the =E2=80=9Cparted=E2=80=9D command operates on the first pa= rtition (=E2=80=9C1=E2=80=9D), yet
for the second command the second partition (=E2=80=9C/dev/sda2=E2=80= =9D) is used.  It=E2=80=99s
better to be consistent here, i.e. to change =E2=80=9Cset 1 esp on=E2= =80=9D to =E2=80=9Cset 2
esp on=E2=80=9D and to state that this would modify =E2=80=9C/dev/sda= 2=E2=80=9D.

Finally, it is not clear where the efi partition should be mounted.
Should it be /mnt/boot/efi?  If so, should the configuration fil= e
specify =E2=80=9C/mnt/boot/efi=E2=80=9D as the target?  Or shoul= d it be =E2=80=9C/boot/efi=E2=80=9D?

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 si= milar.

I've just looked around and found that we have ovmf in ou= r 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 wor= king testcase.
WDYT? 
 

--
Ricardo

<= br>


--_----------=_151752019230130522--