From a8f3814a7b070ec4b8fcdf6960bd9e31824d91a5 Mon Sep 17 00:00:00 2001 From: Xi Ruoyao Date: Sat, 1 Oct 2022 12:41:42 +0800 Subject: [PATCH] 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. --- chapter07/introduction.xml | 2 +- chapter07/kernfs.xml | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/chapter07/introduction.xml b/chapter07/introduction.xml index 62a428416..d00f3fe2a 100644 --- a/chapter07/introduction.xml +++ b/chapter07/introduction.xml @@ -18,7 +18,7 @@ For proper operation of the isolated environment, some communication with the running kernel must be established. This is done via the - so-called Virtual Kernel File Systems, which must be + so-called Virtual Kernel File Systems, which will be mounted before entering the chroot environment. You may want to verify that they are mounted by issuing the findmnt command. diff --git a/chapter07/kernfs.xml b/chapter07/kernfs.xml index 56521ea20..54b864130 100644 --- a/chapter07/kernfs.xml +++ b/chapter07/kernfs.xml @@ -18,8 +18,8 @@ systems exported 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 - memory. These file systems must exist in the $LFS directory tree - before you can chroot successfully. + memory. These file systems must be mounted in the $LFS directory tree + so the applications can find them in the chroot environment. Begin by creating directories on which the file systems will be mounted: