* Merged newxml into HEAD

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3435 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

1 files changed, 67 insertions, 0 deletions

diff --git a/chapter06/introduction.xml b/chapter06/introduction.xml
new file mode 100644
index 000000000..4e0ef7cbb
--- /dev/null
+++ b/chapter06/introduction.xml
@@ -0,0 +1,67 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
+  <!ENTITY % general-entities SYSTEM "../general.ent">
+  %general-entities;
+]>
+<sect1 id="ch-system-introduction">
+<title>Introduction</title>
+<?dbhtml filename="introduction.html"?>
+
+<para>In this chapter we enter the building site, and start
+constructing our LFS system in earnest. That is, we chroot into
+our temporary mini Linux system, create some auxiliary things,
+and then start installing all the packages, one by one.</para>
+ 
+<para>The installation of all this software is pretty straightforward,
+and you will probably think it would be much shorter to give here
+the generic installation instructions and explain in full only the
+installation of those packages that require an alternate method.
+Although we agree with that, we nevertheless choose to give the 
+full instructions for each and every package, simply to minimize
+the possibilities for mistakes.</para>
+
+<para>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 this purpose for every installed package a summary of its content is
+given followed by concise descriptions of each program and library it
+installed.</para>
+
+<para>If you plan to use compiler optimizations in this chapter, take a look at
+the optimization hint at <ulink url="&hints-root;optimization.txt"/>. Compiler
+optimizations can make a program run slightly faster, but they may also cause
+compilation difficulties and even problems when running the program. If a
+package refuses to compile when using optimization, try to compile it without
+optimization and see if the problem goes away. Even if the package does compile
+when using optimization, there is the risk it may have been compiled incorrectly
+due to complex interactions between the code and build tools. In short, the
+small potential gains achieved in using compiler optimization are generally
+outweighed by the risk. First time builders of LFS are encouraged to build
+without custom optimizations. Your system will still be very fast and very
+stable at the same time.</para>
+
+<para>The order in which packages are installed in this chapter has
+to be strictly followed, to ensure that no program gets a path referring
+to <filename class="directory">/tools</filename> hard-wired into it.
+For the same reason, <emphasis>do not </emphasis> compile packages
+in parallel. Compiling in parallel may save you some 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>
+
+<para>Before the installation instructions each installation page gives some
+information about the package: a concise description of what it contains,
+approximately how long it will take to build it, how much disk space it needs
+during this building process, the official download location of the package
+(in case you just want to update a few of them), and which other packages it
+needs in order to be built successfully. After the installation instructions
+follows a list of programs and libraries that the package installs, together
+with a series of short descriptions of these.</para>
+
+<para>If you wish to keep track of which package installs what files, you may
+want to use a package manager. For a general overview of package managers have
+a look at <ulink url="&blfs-root;view/cvs/introduction/pkgmgt.html"/>. And for
+a package management method specifically geared towards LFS see
+<ulink url="&hints-root;more_control_and_pkg_man.txt"/>.</para>
+
+</sect1>