gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-06-25 22:59:19 +01:00
Code Issues Packages Projects Releases Wiki Activity

Correcting idiom / syntax again, based on feedback from Bruce & Doug.

Browse Source
This commit is contained in:
David Bryant 2022-09-22 14:31:32 -05:00
parent b00063f2a5
commit 58f92b0647
1 changed files with 12 additions and 12 deletions

24
chapter02/creatingpartition.xml
View File

@ -94,10 +94,10 @@
<para>Swapping is never good. For mechanical hard drives you can generally
tell if a system is swapping by just listening to disk activity and
observing how the system reacts to commands. With an SSD drive you will not
observing how the system reacts to commands. With an SSD you will not
be able to hear swapping, but you can tell how much swap space is being used
by running the <command>top</command> or <command>free</command> programs. Use of
an SSD drive for a swap partition should be avoided if possible. The first
an SSD for a swap partition should be avoided if possible. The first
reaction to swapping should be to check for an unreasonable command such as
trying to edit a five gigabyte file. If swapping becomes a normal
occurrence, the best solution is to purchase more RAM for your
@ -112,7 +112,7 @@
must be available for GRUB to use during installation of the boot
loader. This partition will normally be labeled 'BIOS Boot' if using
<command>fdisk</command> or have a code of <emphasis>EF02</emphasis> if
using the <command>gdisk</command>.</para>
using the <command>gdisk</command> command.</para>
<note><para>The Grub Bios partition must be on the drive that the BIOS
uses to boot the system. This is not necessarily the drive that holds
@ -155,11 +155,11 @@
needed for the system to run. For LFS a separate partition for
<filename class="directory">/usr</filename> is normally not needed.
If you create it anyway, you should make a partition large enough to
fit all the programs and libraries in the system. The root partition can be
fit all the programs and libraries in the system. The root partition can be
very small (maybe just one gigabyte) in this configuration, so it's
suitable for a thin client or diskless workstation (where
<filename class="directory">/usr</filename> is mounted from a remote
server). However you should be aware that an initramfs (not covered by
server). However, you should be aware that an initramfs (not covered by
LFS) will be needed to boot a system with a separate
<filename class="directory">/usr</filename> partition.</para></listitem>
@ -174,12 +174,12 @@
used, will usually not need to exceed a couple of
gigabytes. If you have enough RAM, you can mount a
<systemitem class='filesystem'>tmpfs</systemitem> on /tmp to make
the accesses to temporary files faster.</para></listitem>
access to temporary files faster.</para></listitem>
<listitem revision='systemd'><para>/tmp &ndash; By default, systemd
mounts a <systemitem class='filesystem'>tmpfs</systemitem> here.
If you want to override the behavior, follow
<xref linkend='systemd-no-tmpfs'/> configuring the LFS
If you want to override that behavior, follow
<xref linkend='systemd-no-tmpfs'/> when configuring the LFS
system.</para></listitem>
<listitem><para>/usr/src &ndash; This partition is very
@ -190,10 +190,10 @@
</itemizedlist>
<para>Any separate partition that you want automatically mounted upon boot
needs to be specified in the <filename>/etc/fstab</filename>. Details
about how to specify partitions will be discussed in <xref
linkend="ch-bootable-fstab"/>. </para>
<para>Any separate partition that you want automatically mounted when the
system starts must be specified in the <filename>/etc/fstab</filename> file.
Details about how to specify partitions will be discussed in <xref
linkend="ch-bootable-fstab"/>.</para>
</sect3>
</sect2>