Changeset a8f3814a for chapter07/introduction.xml

Timestamp:

10/01/2022 05:35:59 AM (19 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/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

0058818

Parents:

36cb08f

git-author:

Xi Ruoyao <xry111@…> (10/01/2022 04:41:42 AM)

git-committer:

Xi Ruoyao <xry111@…> (10/01/2022 05:35:59 AM)

Message:

kernfs: technically, they are not needed for chroot

Chroot command itself does not require kernel VFS mounted. You can mount
/proc, /sys, and /run after entering chroot with
"mount -v -t proc proc /proc" etc. For /dev, if the host kernel
supports devtmpfs, you can also mount /dev in chroot with
"mount -v -t devtmpfs devtmpfs /dev". Even if the host does not support
devtmpfs, it's still possible to mount /proc in chroot, then use
"mount --bind /proc/1/dev /dev".

It's just LFS editors decide to mount them before chroot. So reword
some untrue assertions.

File:

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

chapter07/introduction.xml

@@ -19 +19 @@
   <para>For proper operation of the isolated environment, some communication
   with the running kernel must be established. This is done via the
-  so-called <emphasis>Virtual Kernel File Systems</emphasis>, which must be
+  so-called <emphasis>Virtual Kernel File Systems</emphasis>, which will be
   mounted before entering the chroot environment. You may want to verify
   that they are mounted by issuing the <command>findmnt</command> command.</para>