Changeset fde4f7d for chapter06/devices.xml
- Timestamp:
- 07/01/2005 08:39:25 PM (19 years ago)
- Branches:
- 10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 12.2, 12.2-rc1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- d001e2b
- Parents:
- 4d938ef
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter06/devices.xml
r4d938ef rfde4f7d 31 31 be created dynamically on that virtual filesystem as they are detected or 32 32 accessed. This is generally done during the boot process. Since this new system 33 has not been booted, it is necessary to do what the bootscripts would otherwise34 do by mounting <filename class="directory">/dev</filename>:</para>33 has not been booted, it is necessary to do what the LFS-Bootscripts package would 34 otherwise do by mounting <filename class="directory">/dev</filename>:</para> 35 35 36 36 <screen><userinput>mount -n -t tmpfs none /dev</userinput></screen> … … 52 52 53 53 <para>There are some symlinks and directories required by LFS that are created 54 during system startup by the bootscripts. Since this is a chroot environment and55 not a booted environment, those symlinks and directories need to be created 56 here:</para>54 during system startup by the LFS-Bootscripts package. Since this is a chroot 55 environment and not a booted environment, those symlinks and directories need to 56 be created here:</para> 57 57 58 58 <screen><userinput>ln -s /proc/self/fd /dev/fd
Note:
See TracChangeset
for help on using the changeset viewer.