[Clfs-commits] commit: r4339 - /branches/clfs-sysroot/BOOK/final-system/common/introduction.xml

[svn at cross-lfs.org]

Author: chris at beaker67.com
Date: Mon Jan  5 09:20:31 2009
New Revision: 4339

Log:
Rewrite final-system intro to account for the fact that /tools does not exist in sysroot book

Modified:
    branches/clfs-sysroot/BOOK/final-system/common/introduction.xml

Modified: branches/clfs-sysroot/BOOK/final-system/common/introduction.xml
==============================================================================
--- branches/clfs-sysroot/BOOK/final-system/common/introduction.xml (original)
+++ branches/clfs-sysroot/BOOK/final-system/common/introduction.xml Mon Jan  5 09:20:31 2009
@@ -10,16 +10,15 @@
 
   <title>Introduction</title>
 
-  <para os="a">In this chapter, we enter the building site and start
-  constructing the CLFS system in earnest. The installation of this
-  software is straightforward. Although in many cases the installation
-  instructions could be made shorter and more generic, we have opted
-  to provide the full instructions for every package to minimize the
-  possibilities for mistakes.  The key to learning what makes a Linux
-  system work is to know what each package is used for and why the user
-  (or the system) needs it.  For every installed package, a summary of
-  its contents is given, followed by concise descriptions of each
-  program and library the package installed.</para>
+  <para os="a">In this chapter, we use the cross-compile tools to build
+  the final CLFS system. The installation of this software is
+  straightforward. Although in many cases the installation instructions
+  could be made shorter and more generic, we have opted to provide the full
+  instructions for every package to minimize the possibilities for mistakes.
+  The key to learning what makes a Linux system work is to know what each
+  package is used for and why the user (or the system) needs it. For every
+  installed package, a summary of its contents is given, followed by concise
+  descriptions of each program and library the package installed.</para>
 
   <para os="b">If using compiler optimizations, please review the
   optimization hint at <ulink url="&hints-root;optimization.txt"/>.
@@ -39,14 +38,8 @@
   same time.</para>
 
   <para os="c">The order that packages are installed in this chapter needs to
-  be strictly followed to ensure that no program accidentally acquires a
-  path referring to <filename class="directory">/tools</filename>
-  hard-wired into it. For the same reason, do not compile packages in
-  parallel. Compiling in parallel may save time (especially on dual-CPU
-  machines), but it could result in a program containing a hard-wired
-  path to <filename class="directory">/tools</filename>, which will
-  cause the program to stop working when that directory is
-  removed.</para>
+  be strictly followed to ensure that all package dependencies are
+  fulfilled.</para>
 
   <para os="d">To keep track of which package installs particular files, a
   package manager can be used. For a general overview of different styles of