Changeset da6e70f
- Timestamp:
- 11/26/2022 06:26:21 PM (22 months ago)
- Branches:
- 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 12.2, 12.2-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/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/update-glibc
- Children:
- 38311c3, b1c68c7
- Parents:
- 295e337
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter04/creatingminlayout.xml
r295e337 rda6e70f 9 9 <?dbhtml filename="creatingminlayout.html"?> 10 10 11 <title>Creating a limited directory layout in LFS filesystem</title>11 <title>Creating a Limited Directory Layout in the LFS Filesystem</title> 12 12 13 13 <para>In this section, we begin populating the LFS filesystem with the … … 42 42 <note> 43 43 <para> 44 LFS editors have deliberately decided not to use a44 The LFS editors have deliberately decided not to use a 45 45 <filename class="directory">/usr/lib64</filename> directory. Several 46 steps are taken so that the toolchain doesnot use it. If for any46 steps are taken to be sure the toolchain will not use it. If for any 47 47 reason this directory appears (either because you made an error in 48 following the instructions, or because you install a binary package that49 create s it after finishing LFS), it may break the instructions given in50 the book. You should often ensure that this directory is non-existent.48 following the instructions, or because you installed a binary package that 49 created it after finishing LFS), it may break your system. 50 You should always be sure this directory does not exist. 51 51 </para> 52 52 </note> -
chapter07/creatingdirs.xml
r295e337 rda6e70f 71 71 <warning> 72 72 <para> 73 The FHS does not enforce the existence of the directory73 The FHS does not mandate the existence of the directory 74 74 <filename class="directory">/usr/lib64</filename>, and the LFS editors 75 have decided not to use it. For the instructions in LFS and BLFS to work ,76 it is imperative that this directory be non-existent. You should often77 check that it does not exist, because it is easy to inadvertently78 create it, which will likely break your system.75 have decided not to use it. For the instructions in LFS and BLFS to work correctly, 76 it is imperative that this directory be non-existent. From time to time you should 77 verify that it does not exist, because it is easy to create it 78 inadvertently, and this will probably break your system. 79 79 </para> 80 80 </warning>
Note:
See TracChangeset
for help on using the changeset viewer.