From 295e337887a38caaead4888e441deb620c374e14 Mon Sep 17 00:00:00 2001 From: Pierre Labastie Date: Sat, 26 Nov 2022 09:27:58 +0100 Subject: [PATCH 1/2] Add note and warning about /usr/lib64 --- chapter04/creatingminlayout.xml | 12 ++++++++++++ chapter07/creatingdirs.xml | 11 +++++++++++ 2 files changed, 23 insertions(+) diff --git a/chapter04/creatingminlayout.xml b/chapter04/creatingminlayout.xml index 6b339344b..cab023a49 100644 --- a/chapter04/creatingminlayout.xml +++ b/chapter04/creatingminlayout.xml @@ -39,4 +39,16 @@ esac mkdir -pv $LFS/tools + + + LFS editors have deliberately decided not to use a + /usr/lib64 directory. Several + steps are taken so that the toolchain does not use it. If for any + reason this directory appears (either because you made an error in + following the instructions, or because you install a binary package that + creates it after finishing LFS), it may break the instructions given in + the book. You should often ensure that this directory is non-existent. + + + diff --git a/chapter07/creatingdirs.xml b/chapter07/creatingdirs.xml index 35a0a9003..0bb75fd5d 100644 --- a/chapter07/creatingdirs.xml +++ b/chapter07/creatingdirs.xml @@ -68,6 +68,17 @@ install -dv -m 1777 /tmp /var/tmp directories that are really necessary. However, feel free to create more directories, if you wish. + + + The FHS does not enforce the existence of the directory + /usr/lib64, and the LFS editors + have decided not to use it. For the instructions in LFS and BLFS to work, + it is imperative that this directory be non-existent. You should often + check that it does not exist, because it is easy to inadvertently + create it, which will likely break your system. + + + From da6e70fffedcafb3a31e906155eed21199a71b44 Mon Sep 17 00:00:00 2001 From: David Bryant Date: Sat, 26 Nov 2022 12:26:21 -0600 Subject: [PATCH 2/2] Edited Pierre's recent additons,to improve English idiom. Also corrected capitalization of a title. --- chapter04/creatingminlayout.xml | 12 ++++++------ chapter07/creatingdirs.xml | 10 +++++----- 2 files changed, 11 insertions(+), 11 deletions(-) diff --git a/chapter04/creatingminlayout.xml b/chapter04/creatingminlayout.xml index cab023a49..90c825577 100644 --- a/chapter04/creatingminlayout.xml +++ b/chapter04/creatingminlayout.xml @@ -8,7 +8,7 @@ - Creating a limited directory layout in LFS filesystem + Creating a Limited Directory Layout in the LFS Filesystem In this section, we begin populating the LFS filesystem with the pieces that will constitute the final Linux system. The first step is to @@ -41,13 +41,13 @@ esac - LFS editors have deliberately decided not to use a + The LFS editors have deliberately decided not to use a /usr/lib64 directory. Several - steps are taken so that the toolchain does not use it. If for any + steps are taken to be sure the toolchain will not use it. If for any reason this directory appears (either because you made an error in - following the instructions, or because you install a binary package that - creates it after finishing LFS), it may break the instructions given in - the book. You should often ensure that this directory is non-existent. + following the instructions, or because you installed a binary package that + created it after finishing LFS), it may break your system. + You should always be sure this directory does not exist. diff --git a/chapter07/creatingdirs.xml b/chapter07/creatingdirs.xml index 0bb75fd5d..e2faa08da 100644 --- a/chapter07/creatingdirs.xml +++ b/chapter07/creatingdirs.xml @@ -70,12 +70,12 @@ install -dv -m 1777 /tmp /var/tmp - The FHS does not enforce the existence of the directory + The FHS does not mandate the existence of the directory /usr/lib64, and the LFS editors - have decided not to use it. For the instructions in LFS and BLFS to work, - it is imperative that this directory be non-existent. You should often - check that it does not exist, because it is easy to inadvertently - create it, which will likely break your system. + have decided not to use it. For the instructions in LFS and BLFS to work correctly, + it is imperative that this directory be non-existent. From time to time you should + verify that it does not exist, because it is easy to create it + inadvertently, and this will probably break your system.