Changeset d5cc78a

Timestamp:

03/23/2021 07:24:51 PM (4 years ago)

Author:

Bruce Dubbs <bdubbs@…>

Branches:

11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 12.2, gimp3, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/for-12.3, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/spidermonkey128, xry111/test-20220226, xry111/xf86-video-removal

Children:

5910991c

Parents:

a2c3f1d3

Message:

Editorial changes to new evi pages.

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@24395 af4574ff-66df-0310-9fd7-8a98e5e911e0

Location:

postlfs/filesystems/uefi-bootloaders

Files:

• efibootmgr.xml (modified) (3 diffs)
• efivar.xml (modified) (3 diffs)
• grub-efi.xml (modified) (3 diffs)
• grub-setup.xml (modified) (20 diffs)

postlfs/filesystems/uefi-bootloaders/efibootmgr.xml

@@ -118 +118 @@
     <para>
       <parameter>EFIDIR=LFS</parameter>:
-      This option specify the distro's subdirectory name under
+      This option specifies the distro's subdirectory name under
       <filename class="directory">/boot/efi/EFI</filename>.
       The building system of this package needs it to be set explicitly.
@@ -125 +125 @@
     <para>
       <parameter>EFI_LOADER=grubx64.efi</parameter>:
-      This option specify the name of the default EFI boot loader.  It is
-      set to match the EFI boot loader provided by
-      GRUB<!--xref linkend="grub-efi"/-->.
+      This option specifies the name of the default EFI boot loader.  It is
+      set to match the EFI boot loader provided by GRUB
+      <!--xref linkend="grub-efi"/-->.
     </para>
 
@@ -156 +156 @@
 
       <varlistentry id="efibootdump">
-        <term><command>efibootmgr</command></term>
+        <term><command>efibootdump</command></term>
         <listitem>
           <para>

postlfs/filesystems/uefi-bootloaders/efivar.xml

@@ -90 +90 @@
 
     <para>
-      At first, apply a patch to fix an issue breaking the build with GCC 9
-      or later:
+      First, apply a patch to fix an issue building with GCC 9 or later:
     </para>
 
@@ -97 +96 @@
 
     <para>
-      Build <application>efivar</application> with the following
-      commands:
+      Build <application>efivar</application> with the following commands:
     </para>
 
@@ -132 +130 @@
     <para>
       <parameter>CFLAGS="-O2 -Wno-stringop-truncation"</parameter>:
-      This option overrides the compiler flags defaulted by this package,
-      to avoid build failure.
+      This option overrides the default compiler flags to avoid a build failure.
     </para>
 

postlfs/filesystems/uefi-bootloaders/grub-efi.xml

@@ -123 +123 @@
 
     <para>
-      At first, install font data as the
+      First, install font data as the
       <systemitem class="username">root</systemitem> user:
     </para>
@@ -152 +152 @@
             --with-platform=efi  \
             --disable-werror     &amp;&amp;
-
 make</userinput></screen>
 
     <para>
-      This package does not have a test suite providing meaningful result.
+      This package does not have a test suite providing meaningful results.
     </para>
 
@@ -172 +171 @@
 
     <para>
-      <parameter>--enable-grub-mkfont</parameter>: Built the tool named
-      <command>grub-mkfont</command> to generate font file for the boot
-      loader, from the font data we've installed.
+      <parameter>--enable-grub-mkfont</parameter>: Build the tool named
+      <command>grub-mkfont</command> to generate the font file for the boot
+      loader from the font data we've installed.
     </para>
 
     <warning>
       <para>If the recommended dependency <xref linkend="freetype2"/> is not
-      installed, it's possible to omit this option and build GRUB.  However,
+      installed, it is possible to omit this option and build GRUB.  However,
       if <command>grub-mkfont</command> is not built, or the unicode font
       data is not avaliable at the time GRUB is built, GRUB won't install
       any font for the boot loader.  The GRUB boot menu will be displayed
-      in an ugly way, and the early stage of kernel initialization will be
-      in <quote>blind mode</quote> - you can't see any kernel message before
+      using a coarse font and the early stage of kernel initialization will be
+      in <quote>blind mode</quote> &mdash; you can't see any kernel messages before
       the graphics card driver is initialized.  It will be very difficult to
-      diagnostic some boot issue (especially, if the graphics driver is
-      built as module).</para>
+      diagnose some boot issues, especially if the graphics driver is
+      built as module.</para>
     </warning>
 
     <para>
-      <parameter>--with-platform=efi</parameter>: Ensures to build GRUB with
-      for EFI.
+      <parameter>--with-platform=efi</parameter>: Ensures building GRUB with
+      EFI enabled.
     </para>
 

postlfs/filesystems/uefi-bootloaders/grub-setup.xml

@@ -20 +20 @@
 
     <para>
-      BLFS doesn't have the essential packages to support Secure Boot. To
+      BLFS does not have the essential packages to support Secure Boot. To
       set up the boot process with GRUB for UEFI installed in BLFS, Secure
       Boot must be turned off from the configuration interface of the
@@ -33 +33 @@
     <para>
       Ensure that an emergency boot disk is ready to <quote>rescue</quote>
-      the system, in case the system becomes un-bootable.  To make a
-      emergency boot disk with GRUB for EFI platform, at first find a spare
+      the system in case the system becomes un-bootable.  To make an
+      emergency boot disk with GRUB for an EFI based system, find a spare
       USB flash drive and create a
       <systemitem class="filesystem">vfat</systemitem> file system on it.
@@ -55 +55 @@
     <para>
       Still as the <systemitem class="username">root</systemitem> user, use
-      the CLI of <command>fdisk</command> utility to set the first parition
+      the <command>fdisk</command> utility to set the first parition
       of the USB flash drive to be an <quote>EFI system</quote> partition
       (change <userinput>sdx</userinput> to the device node corresponding
@@ -101 +101 @@
     <para>
       Now the USB flash drive can be used as a emergency boot disk on x86-64
-      UEFI platform.  It will boot the system and show GRUB shell.  Then you
-      can type commands to boot your operation systems on the hard drive.
-      To get how to select the boot device, read the manual of your
+      UEFI platform.  It will boot the system and show the GRUB shell.  Then you
+      can type commands to boot your operating systems on the hard drive.
+      To learn how to select the boot device, read the manual of your
       motherboard or laptop.
     </para>
@@ -145 +145 @@
         <term><parameter>CONFIG_EFI_STUB</parameter></term>
         <listitem>
-          <para>Though EFI stub is designed to boot a kernel directly from
-          the UEFI firmware (without bootloaders like GRUB), GRUB needs the
-          kernel being loaded to support EFI handover protocol enabled by
+          <para>Although the EFI stub is designed to boot a kernel directly from
+          the UEFI firmware (without a bootloader like GRUB), GRUB needs the
+          kernel to be loaded to support the EFI handover protocol enabled by
           this option.</para>
         </listitem>
@@ -155 +155 @@
         <term><parameter>CONFIG_EFI_VARS</parameter></term>
         <listitem>
-          <para>Don't use this option deprecated because of an 1024-byte
+          <para>Don't use this deprecated option because of a 1024-byte
           variable size limit.  Its function is replaced by
           <parameter>CONFIG_EFIVAR_FS</parameter>.</para>
@@ -165 +165 @@
         <listitem>
           <para>The combination of these two options allows the kernel to
-          print debug messages (along with Tux logos) on early stage of boot
-          process with UEFI.</para>
+          print debug messages (along with Tux logos) at the early stage of boot
+          the process with UEFI.</para>
         </listitem>
       </varlistentry>
@@ -179 +179 @@
     <para>
       On EFI based system, the bootloaders are installed in a special FAT32
-      partition called <emphasis>EFI System Partition</emphasis> (ESP).
+      partition called an <emphasis>EFI System Partition</emphasis> (ESP).
       If your system supports EFI, and a recent version of Linux
       distribution or Windows is pre-installed, it's likely that the ESP
@@ -185 +185 @@
       <systemitem class="username">root</systemitem> user, list all the
       partitions on your hard drive (replace <userinput>sda</userinput>
-      with the device node corresponding to the hard drive):
+      with the device corresponding to the appropriate hard drive):
     </para>
 
@@ -196 +196 @@
 
     <para>
-      If the system or the hard drive is new, or it's the first time to
-      install an UEFI booted OS on the system, the ESP may be nonexistent.
-      Then create a new partition, make a
+      If the system or the hard drive is new, or it's a first time 
+      install an UEFI booted OS on the system, the ESP may not exist.
+      In that case, create a new partition, make a
       <systemitem class="filesystem">vfat</systemitem> file system on it,
-      and set the partition type to <quote>EFI system</quote>.  Read the
+      and set the partition type to <quote>EFI system</quote>.  See the
       instructions for the emergency boot device above as a reference.
     </para>
@@ -222 +222 @@
 
     <para>
-      It's recommended to add an entry for the ESP in
+      Add an entry for the ESP in
       <filename>/etc/fstab</filename>, so it will be mounted automatically
       during system boot:
@@ -237 +237 @@
 
     <para>
-      The installation of GRUB on UEFI platform requires the EFI Variable
-      file system (<systemitem class="filesystem">efivarfs</systemitem>)
+      The installation of GRUB on a UEFI platform requires that the EFI Variable
+      file system, <systemitem class="filesystem">efivarfs</systemitem>, to be
       mounted.  As the <systemitem class="username">root</systemitem> user:
     </para>
@@ -248 +248 @@
         If the system is booted with UEFI and systemd,
         <systemitem class="filesystem">efivarfs</systemitem> will be mounted
-        automatically.  However in LFS chroot environment it still needs to
+        automatically.  However in the LFS chroot environment it still needs to
         be mounted manually.
       </para>
@@ -254 +254 @@
 
     <para revision="sysv">
-      It's recommended to add an entry for the
+      Now add an entry for the
       <systemitem class="filesystem">efivarfs</systemitem> in
-      <filename>/etc/fstab</filename>, so it will be mounted automatically
+      <filename>/etc/fstab</filename> so it will be mounted automatically
       during system boot:
     </para>
@@ -279 +279 @@
     <para>
       On UEFI based systems, GRUB works by installing an EFI application
-      (a special kind of PE executable) into
+      (a special kind of executable) into
       <filename class="directory">/boot/efi/EFI/[id]/grubx64.efi</filename>,
       where <filename class="directory">/boot/efi</filename> is the mount
       point of the ESP, and <literal>[id]</literal> is replaced with an
       identifier specified in the <command>grub-install</command> command
-      line.  Then GRUB will create an entry in the EFI variables containing
-      the path <literal>EFI/[id]/grubx64.efi</literal>, so the EFI firmware
+      line.  GRUB will create an entry in the EFI variables containing
+      the path <literal>EFI/[id]/grubx64.efi</literal> so the EFI firmware
       can find <filename>grubx64.efi</filename> and load it.
     </para>
@@ -291 +291 @@
     <para>
       <filename>grubx64.efi</filename> is very lightweight (136 KB with
-      GRUB-2.06~rc1) so it won't cost much space in the ESP.  A typical ESP
-      size is 100 MB (for Windows boot manager, which cost about 50 MB in
+      GRUB-2.06~rc1) so it will not use much space in the ESP.  A typical ESP
+      size is 100 MB (for Windows boot manager, which uses about 50 MB in
       the ESP). Once <filename>grubx64.efi</filename> loaded by the
       firmware, it will load GRUB modules in the boot partition.
@@ -302 +302 @@
       As the <systemitem class="username">root</systemitem> user, install
       the GRUB files into <filename>/boot/efi/EFI/LFS/grubx64.efi</filename>
-      and <filename class="directory">/boot/grub</filename>, and set up the
+      and <filename class="directory">/boot/grub</filename>. Then set up the
       boot entry in the EFI variables:
     </para>
@@ -331 +331 @@
 
     <para>
-      Note that <literal>0005</literal> is the first in
+      Note that <literal>0005</literal> is the first in the
       <literal>BootOrder</literal>, and <literal>Boot0005</literal>
-      is <literal>LFS</literal>.  So on the next boot, GRUB installed
-      by LFS will be used to boot the system.
+      is <literal>LFS</literal>. This means that on the next boot, the 
+      version of GRUB installed by LFS will be used to boot the system.
     </para>
 
@@ -384 +384 @@
       <para>
         From GRUB's perspective, the files are relative to the partition
-        used. If you used a separate /boot partition, remove /boot from the
+        are used. If you used a separate /boot partition, remove /boot from the
         above paths (to kernel and to <filename>unicode.pf2</filename>). You
         will also need to change the set root line to point to the boot
@@ -418 +418 @@
     <para>
       <literal>(hd0,1)</literal> should be replaced with the GRUB
-      designated name for the ESP.  <literal>chainloader</literal>
+      designated name for the ESP.  The <literal>chainloader</literal>
       directive can be used to tell GRUB to run another EFI executable,
       in this case the Windows Boot Manager. You may put more usable tools