Changeset b59b371 for chapter07

Timestamp:

11/19/2022 08:27:13 AM (20 months ago)

Author:

Xi Ruoyao <xry111@…>

Branches:

xry111/clfs-ng

Children:

2ef64c4

Parents:

4d3f41c (diff), 651f491 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.

Message:

Merge remote-tracking branch 'origin/trunk' into xry111/clfs-ng

Location:

chapter07

Files:

• chroot.xml (modified) (1 diff)
• cleanup.xml (modified) (4 diffs)
• createfiles.xml (modified) (4 diffs)
• kernfs.xml (modified) (2 diffs)

chapter07/chroot.xml

@@ -53 +53 @@
 
   <para>The <parameter>-i</parameter> option given to the <command>env</command>
-  command will clear all variables of the environment. After that, only
+  command will clear all the variables in the environment. After that, only
   the <envar>HOME</envar>, <envar>TERM</envar>, <envar>PS1</envar>, and
   <envar>PATH</envar> variables are set again. The
   <parameter>TERM=$TERM</parameter> construct will set the <envar>TERM</envar>
   variable to the default value specified by <command>agetty</command>. This variable is
-  needed for programs like <command>vim</command> and <command>less</command>
-  to operate properly.  If other variables are desired, such as
+  needed so programs like <command>vim</command> and <command>less</command>
+  can operate properly.  If other variables are desired, such as
   <envar>CFLAGS</envar> or <envar>CXXFLAGS</envar>, this is a good place to set
-  them again.</para>
+  them.</para>
 
   <para>Notice that <filename class="directory">/tools/bin</filename> is not
   in the <envar>PATH</envar>. This means that the cross toolchain will no longer be
-  used on the target machine.</para>
+  used.</para>
 
   <para>Note that the <command>bash</command> prompt will say

chapter07/cleanup.xml

@@ -14 +14 @@
     <title>Cleaning</title>
 
-    <para>First, remove the currently installed documentation to prevent them
+    <para>First, remove the currently installed documentation files to prevent them
     from ending up in the final system, and to save about 35 MB:</para>
 
@@ -20 +20 @@
 
     <para>Second, on a modern Linux system, the libtool .la files are only
-    useful for libltdl.  No libraries in LFS are expected to be loaded by
-    libltdl, and it's known that some .la files can cause BLFS packages
-    fail to build.  Remove those files now:</para>
+    useful for libltdl.  No libraries in LFS are loaded by
+    libltdl, and it's known that some .la files can cause BLFS package
+    failures.  Remove those files now:</para>
 
 <screen><userinput>find /usr/{lib,libexec} -name \*.la -delete</userinput></screen>
@@ -43 +43 @@
       backed up for later reuse. In case of fatal failures in the subsequent
       chapters, it often turns out that removing everything and starting over
-      (more carefully) is the best option to recover. Unfortunately, all the
+      (more carefully) is the best way to recover. Unfortunately, all the
       temporary files will be removed, too. To avoid spending extra time to
-      redo something which has been built successfully, creating a backup of
+      redo something which has been done successfully, creating a backup of
       the current LFS system may prove useful.
     </para>
@@ -72 +72 @@
       Note that the instructions below specify the home directory of the host
       system's <systemitem class="username">root</systemitem> user, which is
-      typically found on the root filesystem.
-    </para>
-
-    <para>
+      typically found on the root file system.
       Replace <envar>$HOME</envar> by a directory of your choice if you
       do not want to have the backup stored in <systemitem

chapter07/createfiles.xml

@@ -35 +35 @@
   </indexterm>
 
-  <para>Historically, Linux maintains a list of the mounted file systems in the
+  <para>Historically, Linux maintained a list of the mounted file systems in the
   file <filename>/etc/mtab</filename>. Modern kernels maintain this list
   internally and expose it to the user via the <filename
   class="directory">/proc</filename> filesystem. To satisfy utilities that
-  expect the presence of <filename>/etc/mtab</filename>, create the following
+  expect to find <filename>/etc/mtab</filename>, create the following
   symbolic link:</para>
 
@@ -160 +160 @@
   <para>The created groups are not part of any standard&mdash;they are groups
   decided on in part by the requirements of the Udev configuration in Chapter
-  9, and in part by common convention employed by a number of existing Linux
+  9, and in part by common conventions employed by a number of existing Linux
   distributions. In addition, some test suites rely on specific users or
   groups.  The Linux Standard Base (LSB, available at <ulink
@@ -166 +166 @@
   besides the group <systemitem class="groupname">root</systemitem> with a
   Group ID (GID) of 0, a group <systemitem class="groupname">bin</systemitem>
-  with a GID of 1 be present. The GID of 5 is widely used for
+  with a GID of 1 be present. The GID of 5 is widely used for the
   <systemitem class="groupname">tty</systemitem> group, and the number 5 is
   also used in <phrase revision="systemd">systemd</phrase>
@@ -180 +180 @@
   machine or in the separate namespace).  We assign
   <systemitem class="username">nobody</systemitem> and
-  <systemitem class="groupname">nogroup</systemitem> for it to avoid an
+  <systemitem class="groupname">nogroup</systemitem> to avoid an
   unnamed ID.  But other distros may treat this ID differently, so any
   portable program should not depend on this assignment.</para>

chapter07/kernfs.xml

@@ -16 +16 @@
 
     <para>Applications running in user space utilize various file 
-    systems exported by the kernel to communicate 
+    systems created by the kernel to communicate 
     with the kernel itself. These file systems are virtual: no disk
-    space is used for them. The content of the file systems resides in
+    space is used for them. The content of these file systems resides in
     memory.</para>
 
-    <para>Begin by creating directories on which the file systems will be
+    <para>Begin by creating the directories on which these virtual file systems will be
     mounted:</para>
 
@@ -31 +31 @@
     <para>The kernel has already mounted
     <systemitem class="filesystem">devtmpfs</systemitem>.
-    Mount the remaining virtual kernel filesystems:</para>
+    Mount the remaining virtual kernel file systems:</para>
 
 <screen><userinput>mkdir -pv /dev/{pts,shm}