diff options
| author | Xi Ruoyao <xry111@xry111.site> | 2022-10-01 12:41:42 +0800 |
|---|---|---|
| committer | Xi Ruoyao <xry111@xry111.site> | 2022-10-01 13:35:59 +0800 |
| commit | a8f3814a7b070ec4b8fcdf6960bd9e31824d91a5 (patch) | |
| tree | 9ddd9d0ef84104a27c8b37f420cdcf68a1c9a201 /chapter07/kernfs.xml | |
| parent | 36cb08fbf0b27b76bc319409f712d0944b4b5354 (diff) | |
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.
Diffstat (limited to 'chapter07/kernfs.xml')
| -rw-r--r-- | chapter07/kernfs.xml | 4 |
1 files changed, 2 insertions, 2 deletions
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 <command>chroot</command> successfully.</para> + memory. These file systems must be mounted in the $LFS directory tree + so the applications can find them in the chroot environment.</para> <para>Begin by creating directories on which the file systems will be mounted:</para> |