Trunk is now identical to Testing

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

7 files changed, 245 insertions, 19 deletions

diff --git a/prologue/audience.xml b/prologue/audience.xml
index 2d2edf45d..b9a1842a1 100644
--- a/prologue/audience.xml
+++ b/prologue/audience.xml
@@ -7,6 +7,85 @@
 <title>Audience</title>
 <?dbhtml filename="audience.html"?>
 
-<para>See testing</para>
+<para>There are many reasons why somebody would want to read this
+book. The principle reason is to install a Linux system straight
+from the source code. A question many people raise is, <quote>why go
+through all the hassle of manually building a Linux system from
+scratch when you can just download and install an existing
+one?</quote> That is a good question and is the impetus for this
+section of the book.</para>
+
+<para>One important reason for LFS's existence is to help people learn
+how a Linux system works from the inside out. Building an LFS system
+helps demonstrate what makes Linux tick, and how things work together
+and depend on each other. One of the best things that this learning
+experience provides is the ability to customize Linux to your own
+tastes and needs.</para>
+
+<para>A key benefit of LFS is that it allows users to have more
+control over the system without relying on someone else's Linux
+implementation.  With LFS, <emphasis>you</emphasis> are in the
+driver's seat and dictate every aspect of the system, such as the
+directory layout and bootscript setup. You also dictate where, why,
+and how programs are installed.</para>
+
+<para>Another benefit of LFS is the ability to create a very compact
+Linux system. When installing a regular distribution, one is often
+forced to install several programs which are probably never used.
+These programs waste precious disk space, or worse, CPU cycles. It is
+not difficult to build an LFS system of less than 100 megabytes (MB),
+which is substantially smaller compared to most existing setups.  Does
+this still sound like a lot of space? A few of us have been working on
+creating a very small embedded LFS system. We successfully built a
+system that was specialized to run the Apache web server with
+approximately 8MB of disk space used. Further stripping could bring
+this down to 5 MB or less.  Try that with a regular distribution!
+This is only one of the many benefits of designing your own Linux
+implementation.</para>
+
+<para>We could compare Linux distributions to a hamburger purchased at
+a fast-food restaurant&mdash;you have no idea what might be in what
+you are eating. LFS, on the other hand, does not give you a hamburger.
+Rather, LFS provides the recipe to make the exact hamburger desired.
+This allows users to review the recipe, omit unwanted ingredients, and
+add your own ingredients to enhance the flavor of the burger.
+When you are satisfied with the recipe, move on to preparing it. It
+can be made to exact specifications&mdash;broil it, bake it, deep-fry
+it, or barbecue it.</para>
+
+<para>Another analogy that we can use is that of comparing LFS with a
+finished house. LFS provides the skeletal plan of a house, but it is up
+to you to build it. LFS maintains the freedom to adjust plans
+throughout the process, customizing it to the user's needs and
+preferences.</para>
+
+<para>An additional advantage of a custom built Linux system is
+security. By compiling the entire system from source code, you are
+empowered to audit everything and apply all the security patches
+desired. It is no longer necessary to wait for somebody else to
+compile binary packages that fix a security hole. Unless you
+examine the patch and implement it yourself, you have no guarantee
+that the new binary package was built correctly and adequately fixes
+the problem.</para>
+
+<para>The goal of Linux From Scratch is to build a complete and usable
+foundation-level system. Readers who do not wish to build their own
+Linux system from scratch may not benefit from the information in this
+book. If you only want to know what happens while the computer boots,
+we recommend the <quote>From Power Up To Bash Prompt</quote> HOWTO
+located at <ulink url="http://axiom.anu.edu.au/~okeefe/p2b/"/> or on
+The Linux Documentation Project's (TLDP) website at <ulink
+url="http://www.tldp.org/HOWTO/From-PowerUp-To-Bash-Prompt-HOWTO.html"/>.
+The HOWTO builds a system which is similar to that of this book,
+but it focuses strictly on creating a system capable of booting to a
+BASH prompt. Consider your objective. If you wish to build a Linux
+system while learning along the way, then this book is your best
+choice.</para> 
+
+<para>There are too many good reasons to build your own LFS system to
+list them all here. This section is only the tip of the iceberg. As
+you continue in your LFS experience, you will find the power that
+information and knowledge truly bring.</para>
 
 </sect1>
+
diff --git a/prologue/bookinfo.xml b/prologue/bookinfo.xml
index 1fbf9e04d..2aca11534 100644
--- a/prologue/bookinfo.xml
+++ b/prologue/bookinfo.xml
@@ -14,20 +14,12 @@
 
 
 <copyright id="copyright">
-	<year>1999-2005</year>
+	<year>1999&ndash;2005</year>
 	<holder>Gerard Beekmans</holder>
 </copyright>
 
-
-<abstract>
-<para><note><para>In this book there is only the commands to build an LFS system
-and new stuff. For a full version with all the explanations see <ulink
-url="&lfs-root;lfs/view/testing"/>.</para></note></para>
-</abstract>
-
-
 <legalnotice>
-<para>Copyright (c) 1999-2005, Gerard Beekmans</para>
+<para>Copyright (c) 1999&ndash;2005, Gerard Beekmans</para>
 
 <para>All rights reserved.</para>
 
@@ -38,14 +30,14 @@ met:</para>
 <itemizedlist>
 
 <listitem><para>Redistributions in any form must retain the above copyright 
-notice, this list of conditions and the following disclaimer.</para></listitem>
+notice, this list of conditions and the following disclaimer</para></listitem>
 
 <listitem><para>Neither the name of <quote>Linux From Scratch</quote> nor the
 names of its contributors may be used to endorse or promote products derived
-from  this material without specific prior written permission.</para></listitem>
+from  this material without specific prior written permission</para></listitem>
 
 <listitem><para>Any material derived from Linux From Scratch must contain 
-a reference to the <quote>Linux From Scratch</quote> project.</para></listitem>
+a reference to the <quote>Linux From Scratch</quote> project</para></listitem>
 
 </itemizedlist>
 
@@ -62,5 +54,5 @@ NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
 SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.</para>
 </legalnotice>
 
-
 </bookinfo>
+
diff --git a/prologue/dedication.xml b/prologue/dedication.xml
index a523b2936..41cca4d77 100644
--- a/prologue/dedication.xml
+++ b/prologue/dedication.xml
@@ -7,3 +7,4 @@
 <title>Dedication</title>
 <para>This book is dedicated</para>
 </dedication>
+
diff --git a/prologue/foreword.xml b/prologue/foreword.xml
index c9aaf7242..7f2c31288 100644
--- a/prologue/foreword.xml
+++ b/prologue/foreword.xml
@@ -7,6 +7,61 @@
 <title>Foreword</title>
 <?dbhtml filename="foreword.html"?>
 
-<para>See testing</para>
+<para>My adventures in Linux began six years ago when I downloaded and
+installed my first distribution. After working with it for awhile, I
+discovered issues I definitely would have liked to see improved upon.
+For example, I didn't like the arrangement of the bootscripts or the way
+programs were configured by default. I tried a number of alternate
+distributions to address these issues, yet each had its pros and cons.
+Finally, I realized that if I wanted full satisfaction from my Linux
+system, I would have to build my own from scratch.</para>
+
+<para>What does this mean? I resolved not to use pre-compiled packages
+of any kind, nor CD-ROMs or boot disks that would install basic
+utilities. I would use my current Linux system to develop my own
+customized system. This <quote>perfect</quote> Linux system would then
+have the strengths of various systems without their associated
+weaknesses. In the beginning, the idea was rather daunting, but I
+remained committed to the idea that a system could be built that would
+conform to my needs and desires rather than to a standard that just
+did not fit what I was looking for.</para>
+
+<para>After sorting through issues such as circular dependencies and
+compile-time errors, I created a custom-built Linux system that was
+fully operational and suitable to individual needs. This process also
+allowed me to create compact and streamlined Linux systems which are
+faster and take up less space than traditional operating systems. I
+called this system a Linux From Scratch system, or an LFS system for
+short.</para>
+
+<para>As I shared my goals and experiences with other members of the
+Linux community, it became apparent that there was sustained interest
+in the ideas set forth in my Linux adventures. Such custom-built LFS
+systems not only to meet user specifications and requirements, but
+also serve as an ideal learning opportunity for programmers and system
+administrators to enhance their Linux skills. Out of this broadened
+interest, the Linux From Scratch Project was born.</para>
+
+<para>This <emphasis>Linux From Scratch</emphasis> book provides
+readers with the background and instruction to design and build custom
+Linux systems. This book highlights the Linux from Scratch project and
+the benefits of using this system. Users can dictate all aspects of
+their system, including directory layout, script setup, and security.
+The resulting system will be compiled straight from the source code,
+and the user will be able to specify where, why, and how programs are
+installed. This book allows readers to fully customize Linux systems
+to their own needs and allows users more control over their
+system.</para>
+
+<para>I hope you will have a great time working on your own LFS
+system, and enjoy the numerous benefits of having a system that is
+truly <emphasis>your own</emphasis>.</para>
+
+<para></para>
+
+<literallayout>--
+Gerard Beekmans
+gerard@linuxfromscratch.org</literallayout>
 
 </sect1>
+
diff --git a/prologue/organization.xml b/prologue/organization.xml
index 70d8572e4..f701fc388 100644
--- a/prologue/organization.xml
+++ b/prologue/organization.xml
@@ -7,6 +7,34 @@
 <title>Structure</title>
 <?dbhtml filename="organization.html"?>
 
-<para>See testing</para>
+<para>This book is divided into the following parts.</para>
+
+<sect2>
+<title>Part I - Introduction</title>
+
+<para>Part I explains a few important notes on how to proceed with the
+LFS installation.  This section also provides meta-information about
+the book.</para>
+</sect2>
+
+<sect2>
+<title>Part II - Preparing for the Build</title>
+
+<para>Part II describes how to prepare for the building process&mdash;making
+a partition, downloading the packages, and compiling temporary
+tools.</para>
+</sect2>
+
+<sect2>
+<title>Part III - Building the LFS System</title>
+
+<para>Part III guides the reader through the building of the LFS
+system&mdash;compiling and installing all the packages one by one,
+setting up the boot scripts, and installing the kernel. The resulting
+Linux system is the foundation on which other software can be built to
+expand the system as desired. At the end of this book, there is an
+easy to use reference listing all of the programs, libraries, and
+important files that have been installed.</para>
+</sect2>
 
 </sect1>
diff --git a/prologue/prerequisites.xml b/prologue/prerequisites.xml
index b22902560..506fe4487 100644
--- a/prologue/prerequisites.xml
+++ b/prologue/prerequisites.xml
@@ -7,6 +7,31 @@
 <title>Prerequisites</title>
 <?dbhtml filename="prerequisites.html"?>
 
-<para>See testing</para>
+<para>This book assumes that the reader has a reasonable knowledge of using
+and installing Linux software. Before building an LFS system, we
+recommend reading the following HOWTOs:</para>
+
+<itemizedlist>
+<listitem><para remap="verbatim">Software-Building-HOWTO
+<ulink url="http://www.tldp.org/HOWTO/Software-Building-HOWTO.html"/></para>
+
+<para>This is a comprehensive guide to building and installing
+<quote>generic</quote> Unix software distributions under Linux.</para></listitem>
+
+<listitem><para remap="verbatim">The Linux Users' Guide
+<ulink url="http://espc22.murdoch.edu.au/~stewart/guide/guide.html"/></para>
+
+<para>This guide covers the usage of assorted Linux software.</para></listitem>
+
+<listitem><para remap="verbatim">The Essential Pre-Reading Hint
+<ulink url="&hints-root;essential_prereading.txt"/></para>
+
+<para>This is an LFS Hint written specifically for users new to Linux.
+It includes a list of links to excellent sources of information on a
+wide range of topics. Anyone attempting to install LFS should have an
+understanding of many of the topics in this hint.</para></listitem>
+
+</itemizedlist>
 
 </sect1>
+
diff --git a/prologue/typography.xml b/prologue/typography.xml
index d13d31282..3a74378a4 100644
--- a/prologue/typography.xml
+++ b/prologue/typography.xml
@@ -7,6 +7,52 @@
 <title>Typography</title>
 <?dbhtml filename="typography.html"?>
 
-<para>See testing</para>
+<para>To make things easier to follow, there are a few typographical
+conventions used throughout this book. This section contains some
+examples of the typographical format found throughout Linux From
+Scratch.</para>
+
+<screen><userinput>./configure --prefix=/usr</userinput></screen>
+
+<para>This form of text is designed to be typed exactly as seen unless
+otherwise noted in the surrounding text. It is also used in the
+explanation sections to identify which of the commands is being
+referenced.</para>
+
+<screen><computeroutput>install-info: unknown option '--dir-file=/mnt/lfs/usr/info/dir'</computeroutput></screen>
+
+<para>This form of text (fixed width text) shows screen output,
+probably as the result of commands issued.  This format is also used
+to show filenames, such as
+<filename>/etc/ld.so.conf</filename>.</para>
+
+<para><emphasis>Emphasis</emphasis></para>
+
+<para>This form of text is used for several purposes in the book,
+mainly to emphasize important points or items.</para>
+
+<para><ulink url="&lfs-root;"/></para>
+
+<para>This format is used for hyperlinks, both within the LFS
+community and to external pages, including HOWTOs, download locations,
+and websites.</para>
+
+<screen><userinput>cat &gt; $LFS/etc/group &lt;&lt; "EOF"
+<literal>root:x:0:
+bin:x:1:
+......</literal>
+EOF</userinput></screen>
+
+<para>This format is used when creating configuration files. The first
+command tells the system to create the file
+<filename>$LFS/etc/group</filename> from whatever is typed on the
+following lines until the sequence end of file (EOF) is encountered.
+Therefore, this entire section is generally typed as seen.</para>
+
+<para><replaceable>[REPLACED TEXT]</replaceable></para>
+
+<para>This format is used to encapsulate text that is not to be typed
+as seen<phrase condition="html"> or copy-and-pasted</phrase>.</para>
 
 </sect1>
+