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

Cleaned up verbiage in unnumbered intro to part 3 (chapters 5 et seq).

Browse Source
This commit is contained in:
David Bryant 2022-09-28 11:26:36 -05:00
parent ef93b66006
commit dd7f9df19f
1 changed files with 14 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
part3intro/introduction.xml
View File

@ -10,25 +10,25 @@
<title>Introduction</title>
<para>This part is divided into three stages: first building a cross
compiler and its associated libraries; second, use this cross toolchain
<para>This part is divided into three stages: first, building a cross
compiler and its associated libraries; second, using this cross toolchain
to build several utilities in a way that isolates them from the host
distribution; third, enter the chroot environment, which further improves
host isolation, and build the remaining tools needed to build the final
distribution; and third, entering the chroot environment (which further improves
host isolation) and constructing the remaining tools needed to build the final
system.</para>
<important><para>With this part begins the real work of building a new
system. It requires much care in ensuring that the instructions are
followed exactly as the book shows them. You should try to understand
what they do, and whatever your eagerness to finish your build, you should
refrain from blindly type them as shown, but rather read documentation when
<important><para>This is where the real work of building a new system
begins. Be very careful to follow the instructions exactly as the book
shows them. You should try to understand what each command does,
and no matter how eager you are to finish your build, you should
refrain from blindly typing the commands as shown. Read the documentation when
there is something you do not understand. Also, keep track of your typing
and of the output of commands, by sending them to a file, using the
<command>tee</command> utility. This allows for better diagnosing
if something gets wrong.</para></important>
and of the output of commands, by using the <command>tee</command> utility
to send the terminal output to a file. This makes debugging easier
if something goes wrong.</para></important>
<para>The next section gives a technical introduction to the build process,
while the following one contains <emphasis role="strong">very
<para>The next section is a technical introduction to the build process,
while the following one presents <emphasis role="strong">very
important</emphasis> general instructions.</para>
</sect1>