Changeset 29526d3
- Timestamp:
- 09/30/2022 05:27:55 PM (18 months ago)
- 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:
- 36cb08f
- Parents:
- 52ddd6c
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter07/kernfs.xml
r52ddd6c r29526d3 15 15 </indexterm> 16 16 17 <para>Various file systems exported by the kernel are used to communicate to 18 and from the kernel itself. These file systems are virtual in that no disk 17 <para>Applications running in user space utilize various file 18 systems exported by the kernel to communicate 19 with the kernel itself. These file systems are virtual: no disk 19 20 space is used for them. The content of the file systems resides in 20 memory.</para> 21 memory. These file systems must exist in the $LFS directory tree 22 before you can <command>chroot</command> successfully.</para> 21 23 22 <para>Begin by creating directories on towhich the file systems will be24 <para>Begin by creating directories on which the file systems will be 23 25 mounted:</para> 24 26 … … 30 32 <para>During a normal boot, the kernel automatically mounts the 31 33 <systemitem class="filesystem">devtmpfs</systemitem> filesystem on the 32 <filename class="directory">/dev</filename> directory , and allowthe33 devices to be created dynamically on that virtual filesystem asthey34 are detected or accessed. Device creation is generally done during the35 boot process by the kernel and Udev.36 Since th is new system does not yet have Udev and34 <filename class="directory">/dev</filename> directory; the 35 devices are created dynamically on that virtual filesystem when they 36 are first detected or accessed. Device creation is generally done during the 37 boot process by the kernel and the udev program. 38 Since the new system does not yet include udev and 37 39 has not yet been booted, it is necessary to mount and populate 38 <filename class="directory">/dev</filename>manually. This is40 the <filename class="directory">/dev</filename> directory manually. This is 39 41 accomplished by bind mounting the host system's 40 42 <filename class="directory">/dev</filename> directory. A bind mount is 41 43 a special type of mount that allows you to create a mirror of a 42 directory or mount point tosome other location. Use the following43 command to achievethis:</para>44 directory or mount point at some other location. Use the following 45 command to do this:</para> 44 46 45 47 <screen><userinput>mount -v --bind /dev $LFS/dev</userinput></screen> … … 90 92 directory needs to be created.</para> 91 93 92 <para>In other cases <filename>/dev/shm</filename> is a mountpoint94 <para>In other host systems <filename>/dev/shm</filename> is a mount point 93 95 for a tmpfs. In that case the mount of /dev above will only create 94 /dev/shm in the chroot environment as a directory. In this situation95 we explicitly mount a tmpfs,</para>96 /dev/shm as a directory in the chroot environment. In this situation 97 we must explicitly mount a tmpfs:</para> 96 98 97 99 <screen><userinput>if [ -h $LFS/dev/shm ]; then
Note:
See TracChangeset
for help on using the changeset viewer.