Changeset 2f9498af

Timestamp:

11/18/2022 04:52:09 AM (17 months ago)

Author:

Xi Ruoyao <xry111@…>

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/update-glibc

Children:

9407694

Parents:

f714a8f

Message:

kernfs: remove a false note

Things are a little tricky:

1. If the host is "modern" (any desktop distro after 2013), the kernel supports devtmpfs and the host udev will do adjustments to the devtmpfs. All instances of devtmpfs shares the same content so we'll see the work of both the kernel and the host udev in chroot.
2. If the host is old but the kernel supports devtmpfs (i. e. the host is not using devtmpfs for its /dev), when we mount devtmpfs on $LFS/dev we'll see the work of the kernel in chroot, but not the work of udev. Building LFS does not need any work of udev.
3. If the host is very old and the kernel does not support devtmpfs at all, we can't mount devtmpfs.

Mounting a devtmpfs will work for 1 and 2, while bind mounting will work
for 1, 2, and 3. So we use bind mounting here.

I don't want to squash all these details into the book, so just remove
the false statement here.

File:

• chapter07/kernfs.xml (modified) (1 diff)

chapter07/kernfs.xml

@@ -42 +42 @@
       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 (i.e., the udev daemon will do the
-      necessary work automatically).</para>
+      on the kernel to populate it.</para>
 
       <para>But some host kernels lack &devtmpfs; support; these