diff options
| -rw-r--r-- | chapter07/kernfs.xml | 31 | ||||
| -rw-r--r-- | chapter09/udev.xml | 2 | ||||
| -rw-r--r-- | general.ent | 1 |
3 files changed, 23 insertions, 11 deletions
diff --git a/chapter07/kernfs.xml b/chapter07/kernfs.xml index 54b864130..4a1cac179 100644 --- a/chapter07/kernfs.xml +++ b/chapter07/kernfs.xml @@ -29,16 +29,27 @@ <sect2 id="ch-tools-bindmount"> <title>Mounting and Populating /dev</title> - <para>During a normal boot, the kernel automatically mounts the - <systemitem class="filesystem">devtmpfs</systemitem> filesystem on the - <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 - the <filename class="directory">/dev</filename> directory manually. This is - accomplished by bind mounting the host system's + <para>During a normal boot of the LFS system, the kernel automatically + mounts the <systemitem class="filesystem">devtmpfs</systemitem> + filesystem on the + <filename class="directory">/dev</filename> directory; the kernel + creates device on that virtual filesystem 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 + <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 <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 at some other location. Use the following diff --git a/chapter09/udev.xml b/chapter09/udev.xml index 435255a19..396f2b389 100644 --- a/chapter09/udev.xml +++ b/chapter09/udev.xml @@ -93,7 +93,7 @@ </sect3> - <sect3> + <sect3 id='ch-config-udev-device-node-creation'> <title>Device Node Creation</title> <para>Device files are created by the kernel by the <systemitem diff --git a/general.ent b/general.ent index 81a7b51dc..00eea04e1 100644 --- a/general.ent +++ b/general.ent @@ -121,6 +121,7 @@ <!ENTITY root "<systemitem class='username'>root</systemitem>"> <!ENTITY lfs-user "<systemitem class='username'>lfs</systemitem>"> +<!ENTITY devtmpfs "<systemitem class='filesystem'>devtmpfs</systemitem>"> <!ENTITY fstab "<filename>/etc/fstab</filename>"> <!ENTITY boot-dir "<filename class='directory'>/boot</filename>"> <!ENTITY ch-final "<xref linkend='chapter-building-system'/>"> |