diff options
Diffstat (limited to 'chapter07/kernfs.xml')
| -rw-r--r-- | chapter07/kernfs.xml | 42 |
1 files changed, 21 insertions, 21 deletions
diff --git a/chapter07/kernfs.xml b/chapter07/kernfs.xml index 3e96bee5e..48826d06c 100644 --- a/chapter07/kernfs.xml +++ b/chapter07/kernfs.xml @@ -15,13 +15,13 @@ </indexterm> <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. These file systems must be mounted in the $LFS directory tree so the applications can find them in the chroot environment.</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> <screen><userinput>mkdir -pv $LFS/{dev,proc,sys,run}</userinput></screen> @@ -29,31 +29,31 @@ <sect2 id="ch-tools-bindmount"> <title>Mounting and Populating /dev</title> - <para>During a normal boot of the LFS system, the kernel automatically + <para>During a normal boot of an LFS system, the kernel automatically mounts the <systemitem class="filesystem">devtmpfs</systemitem> - filesystem on the + file system on the <filename class="directory">/dev</filename> directory; the kernel - creates device nodes on that virtual filesystem during the boot process + creates device nodes on that virtual file system during the boot process, or when a device is first detected or accessed. The udev daemon may - change the owner or permission of the device nodes created by the - kernel, or create new device nodes or symlinks to ease the work of - distro maintainers or system administrators. (See + change the ownership or permissions of the device nodes created by the + kernel, and create new device nodes or symlinks, to ease the work of + distro maintainers and system administrators. (See <xref linkend='ch-config-udev-device-node-creation'/> for details.) If the host kernel supports &devtmpfs;, we can simply mount a &devtmpfs; at <filename class='directory'>$LFS/dev</filename> and rely - on the kernel to populate it (the LFS building process does not need - the additional work onto &devtmpfs; by udev daemon).</para> - - <para>But, some host kernels may lack &devtmpfs; support and these - host distros maintain the content of - <filename class="directory">/dev</filename> with different methods. - So the only host-agnostic way for populating - <filename class="directory">$LFS/dev</filename> is - bind mounting the host system's + on the kernel to populate it (i.e., the udev daemon will do the + necessary work automatically).</para> + + <para>But some host kernels lack &devtmpfs; support; these + host distros use different methods to create the content of + <filename class="directory">/dev</filename>. + So the only host-agnostic way to populate the + <filename class="directory">$LFS/dev</filename> directory is + 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 + a special type of mount that generates a duplicate copy of a directory or mount point at some other location. Use the following - command to do this:</para> + command to do this.</para> <screen><userinput>mount -v --bind /dev $LFS/dev</userinput></screen> @@ -62,7 +62,7 @@ <sect2 id="ch-tools-kernfsmount"> <title>Mounting Virtual Kernel File Systems</title> - <para>Now mount the remaining virtual kernel filesystems:</para> + <para>Now mount the remaining virtual kernel file systems:</para> <screen><userinput>mount -v --bind /dev/pts $LFS/dev/pts mount -vt proc proc $LFS/proc |