diff options
| author | Xi Ruoyao <xry111@xry111.site> | 2022-11-18 12:52:09 +0800 |
|---|---|---|
| committer | Xi Ruoyao <xry111@xry111.site> | 2022-11-18 12:52:09 +0800 |
| commit | 2f9498afa401af249bb5c2090b3cc393e659ceb0 (patch) | |
| tree | 24fbb72fbf7df4393e141e35921f6491538a66df /chapter07 | |
| parent | f714a8fa3bdd85d28bd9eb49ab0f1f59e39a5054 (diff) | |
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.
Diffstat (limited to 'chapter07')
| -rw-r--r-- | chapter07/kernfs.xml | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/chapter07/kernfs.xml b/chapter07/kernfs.xml index 48826d06c..4ec299708 100644 --- a/chapter07/kernfs.xml +++ b/chapter07/kernfs.xml @@ -41,8 +41,7 @@ <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 (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 host distros use different methods to create the content of |