gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-06-18 19:29:21 +01:00
Code Issues Packages Projects Releases Wiki Activity

Edited Pierre's recent additons,to improve English idiom. Also corrected

Browse Source 
capitalization of a title.
This commit is contained in:
David Bryant 2022-11-26 12:26:21 -06:00
parent 295e337887
commit da6e70fffe
2 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
chapter04/creatingminlayout.xml
View File

@ -8,7 +8,7 @@
<sect1 id="ch-tools-creatingminlayout"> <sect1 id="ch-tools-creatingminlayout">
<?dbhtml filename="creatingminlayout.html"?> <?dbhtml filename="creatingminlayout.html"?>
<title>Creating a limited directory layout in LFS filesystem</title> <title>Creating a Limited Directory Layout in the LFS Filesystem</title>
<para>In this section, we begin populating the LFS filesystem with the <para>In this section, we begin populating the LFS filesystem with the
pieces that will constitute the final Linux system. The first step is to pieces that will constitute the final Linux system. The first step is to
@ -41,13 +41,13 @@ esac</userinput></screen>
<note> <note>
<para> <para>
LFS editors have deliberately decided not to use a The LFS editors have deliberately decided not to use a
<filename class="directory">/usr/lib64</filename> directory. Several <filename class="directory">/usr/lib64</filename> 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 reason this directory appears (either because you made an error in
following the instructions, or because you install a binary package that following the instructions, or because you installed a binary package that
creates it after finishing LFS), it may break the instructions given in created it after finishing LFS), it may break your system.
the book. You should often ensure that this directory is non-existent. You should always be sure this directory does not exist.
</para> </para>
</note> </note>

10
chapter07/creatingdirs.xml
View File

@ -70,12 +70,12 @@ install -dv -m 1777 /tmp /var/tmp</userinput></screen>
<warning> <warning>
<para> <para>
The FHS does not enforce the existence of the directory The FHS does not mandate the existence of the directory
<filename class="directory">/usr/lib64</filename>, and the LFS editors <filename class="directory">/usr/lib64</filename>, and the LFS editors
have decided not to use it. For the instructions in LFS and BLFS to work, 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. You should often it is imperative that this directory be non-existent. From time to time you should
check that it does not exist, because it is easy to inadvertently verify that it does not exist, because it is easy to create it
create it, which will likely break your system. inadvertently, and this will probably break your system.
</para> </para>
</warning> </warning>