Changeset 29526d3

Timestamp:

09/30/2022 05:27:55 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:

36cb08f

Parents:

52ddd6c

Message:

Made grammatical corrections and stylistic changes to chapter 7.3.
Added clarification; the virtual file systems expose certain information
to programs in user space; chroot won't work without them.

File:

• chapter07/kernfs.xml (modified) (3 diffs)

chapter07/kernfs.xml

@@ -15 +15 @@
   </indexterm>
 
-    <para>Various file systems exported by the kernel are used to communicate to
-    and from the kernel itself. These file systems are virtual in that no disk
+    <para>Applications running in user space utilize various file 
+    systems exported 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
-    memory.</para>
+    memory. These file systems must exist in the $LFS directory tree
+    before you can <command>chroot</command> successfully.</para>
 
-    <para>Begin by creating directories onto which the file systems will be
+    <para>Begin by creating directories on which the file systems will be
     mounted:</para>
 
@@ -30 +32 @@
       <para>During a normal boot, the kernel automatically mounts the
       <systemitem class="filesystem">devtmpfs</systemitem> filesystem on the
-      <filename class="directory">/dev</filename> directory, and allow the
-      devices to be created dynamically on that virtual filesystem as they
-      are detected or accessed. Device creation is generally done during the
-      boot process by the kernel and Udev.
-      Since this new system does not yet have Udev and
+      <filename class="directory">/dev</filename> directory; the
+      devices are created dynamically on that virtual filesystem when they
+      are first detected or accessed. Device creation is generally done during the
+      boot process by the kernel and the udev program.
+      Since the new system does not yet include udev and
       has not yet been booted, it is necessary to mount and populate
-      <filename class="directory">/dev</filename> manually. This is
+      the <filename class="directory">/dev</filename> directory manually. This is
       accomplished by bind mounting the host system's
       <filename class="directory">/dev</filename> directory. A bind mount is
       a special type of mount that allows you to create a mirror of a
-      directory or mount point to some other location. Use the following
-      command to achieve this:</para>
+      directory or mount point at some other location. Use the following
+      command to do this:</para>
 
 <screen><userinput>mount -v --bind /dev $LFS/dev</userinput></screen>
@@ -90 +92 @@
       directory needs to be created.</para>
 
-      <para>In other cases <filename>/dev/shm</filename> is a mountpoint 
+      <para>In other host systems <filename>/dev/shm</filename> is a mount point 
       for a tmpfs. In that case the mount of /dev above will only create
-      /dev/shm in the chroot environment as a directory. In this situation
-      we explicitly mount a tmpfs,</para>
+      /dev/shm as a directory in the chroot environment. In this situation
+      we must explicitly mount a tmpfs:</para>
 
 <screen><userinput>if [ -h $LFS/dev/shm ]; then