- Timestamp:
- 02/21/2007 03:44:06 AM (17 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, 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/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- bf610ba
- Parents:
- 659cc3d
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter07/symlinks.xml
r659cc3d r651719a 82 82 at this time, because you have bind-mounted the host's 83 83 <filename class="directory">/dev</filename> directory into the LFS system, 84 and we assume the symlinks exist and are correct on the host. The rules 85 will be created, along with the symlinks, the first time you boot your LFS 86 system.</para> 84 and we assume the symlinks exist on the host. The rules and symlinks will 85 be created the first time you boot your LFS system.</para> 86 87 <para>However, if you have multiple CD-ROM devices, then the symlinks 88 generated at that time may point to different devices than they point to on 89 your host, because devices are not discovered in a predictable order. The 90 assignments created when you first boot the LFS system will be stable, so 91 this is only an issue if you need the symlinks on both systems to point to 92 the same device. If you need that, then inspect (and possibly edit) the 93 generated <filename>/etc/udev/rules.d/70-persistent-cd.rules</filename> 94 file after booting, to make sure the assigned symlinks match what you need.</para> 87 95 88 96 </sect2>
Note:
See TracChangeset
for help on using the changeset viewer.