Changeset 6612f54


Ignore:
Timestamp:
09/21/2022 09:16:00 PM (19 months ago)
Author:
David Bryant <davidbryant@…>
Branches:
11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, bdubbs/gcc13, multilib, renodr/libudev-from-systemd, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
dbab2a4
Parents:
9254148
Message:

Corrected English idiom and punctuation in chapter 2.4 (new partition).

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter02/creatingpartition.xml

    r9254148 r6612f54  
    9595    <para>Swapping is never good. For mechanical hard drives you can generally
    9696    tell if a system is swapping by just listening to disk activity and
    97     observing how the system reacts to commands.  For an SSD drive you will not
    98     be able to hear swapping but you can tell how much swap space is being used
    99     by the <command>top</command> or <command>free</command> programs.  Use of
     97    observing how the system reacts to commands. With an SSD drive you will not
     98    be able to hear swapping, but you can tell how much swap space is being used
     99    by running the <command>top</command> or <command>free</command> programs.  Use of
    100100    an SSD drive for a swap partition should be avoided if possible.  The first
    101101    reaction to swapping should be to check for an unreasonable command such as
     
    113113    loader. This partition will normally be labeled 'BIOS Boot' if using
    114114    <command>fdisk</command> or have a code of <emphasis>EF02</emphasis> if
    115     using <command>gdisk</command>.</para>
     115    using the <command>gdisk</command>.</para>
    116116
    117117    <note><para>The Grub Bios partition must be on the drive that the BIOS
    118     uses to boot the system.  This is not necessarily the same drive where the
    119     LFS root partition is located. Disks on a system may use different
    120     partition table types.  The requirement for this partition depends
     118    uses to boot the system.  This is not necessarily the drive that holds
     119    the LFS root partition. The disks on a system may use different
     120    partition table types. The necessity of the Grub Bios partition depends
    121121    only on the partition table type of the boot disk.</para></note>
    122122    </sect3>
     
    134134      store kernels and other booting information.  To minimize potential boot
    135135      problems with larger disks, make this the first physical partition on
    136       your first disk drive.  A partition size of 200 megabytes is quite
     136      your first disk drive.  A partition size of 200 megabytes is
    137137      adequate.</para></listitem>
    138138
     
    151151      <filename class="directory">/lib</filename>, and
    152152      <filename class="directory">/sbin</filename> are symlinks to their
    153       counterpart in <filename class="directory">/usr</filename>.
    154       So <filename class="directory">/usr</filename> contains all binaries
     153      counterparts in <filename class="directory">/usr</filename>.
     154      So <filename class="directory">/usr</filename> contains all the binaries
    155155      needed for the system to run.  For LFS a separate partition for
    156156      <filename class="directory">/usr</filename> is normally not needed.
    157       If you need it anyway, you should make a partition large enough to
    158       fit all programs and libraries in the system.  The root partition can be
     157      If you create it anyway, you should make a partition large enough to
     158      fit all the programs and libraries in the system.  The root partition can be
    159159      very small (maybe just one gigabyte) in this configuration, so it's
    160160      suitable for a thin client or diskless workstation (where
    161161      <filename class="directory">/usr</filename> is mounted from a remote
    162       server).  However you should take care that an initramfs (not covered by
    163       LFS) will be needed to boot a system with separate
     162      server).  However you should be aware that an initramfs (not covered by
     163      LFS) will be needed to boot a system with a separate
    164164      <filename class="directory">/usr</filename> partition.</para></listitem>
    165165
    166166      <listitem><para>/opt &ndash; This directory is most useful for
    167       BLFS where multiple installations of large packages like Gnome or KDE can
     167      BLFS, where multiple large packages like Gnome or KDE can
    168168      be installed without embedding the files in the /usr hierarchy.  If
    169169      used, 5 to 10 gigabytes is generally adequate.</para>
     
    176176      <listitem><para>/usr/src &ndash; This partition is very
    177177      useful for providing a location to store BLFS source files and
    178       share them across LFS builds.  It can also be used as a location
    179       for building BLFS packages.  A reasonably large partition of 30-50
    180       gigabytes allows plenty of room.</para></listitem>
     178      share them across LFS builds. It can also be used as a location
     179      for building BLFS packages. A reasonably large partition of 30-50
     180      gigabytes provides plenty of room.</para></listitem>
    181181
    182182    </itemizedlist>
    183183
    184184    <para>Any separate partition that you want automatically mounted upon boot
    185     needs to be specified in the <filename>/etc/fstab</filename>.  Details
     185    needs to be specified in the <filename>/etc/fstab</filename>. Details
    186186    about how to specify partitions will be discussed in <xref
    187187    linkend="ch-bootable-fstab"/>.  </para>
Note: See TracChangeset for help on using the changeset viewer.