Index: BOOK/arm-index.xml
===================================================================
--- BOOK/arm-index.xml	(revision 3aed10f5cd26989641844df4b6bbb48db8d9e8dc)
+++ BOOK/arm-index.xml	(revision 193c88a3b3de32aafa97f685bc7fafa806a124a9)
@@ -8,6 +8,6 @@
 <book>
 
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="prologue/arm/bookinfo.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="prologue/preface.xml"/>
+  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="preface/arm/bookinfo.xml"/>
+  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="preface/preface.xml"/>
 
   <part id="part1">
Index: BOOK/mips-index.xml
===================================================================
--- BOOK/mips-index.xml	(revision 3aed10f5cd26989641844df4b6bbb48db8d9e8dc)
+++ BOOK/mips-index.xml	(revision 193c88a3b3de32aafa97f685bc7fafa806a124a9)
@@ -8,6 +8,6 @@
 <book>
 
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="prologue/mips/bookinfo.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="prologue/preface.xml"/>
+  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="preface/mips/bookinfo.xml"/>
+  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="preface/preface.xml"/>
 
   <part id="part1">
Index: BOOK/preface/arm/bookinfo.xml
===================================================================
--- BOOK/preface/arm/bookinfo.xml	(revision 193c88a3b3de32aafa97f685bc7fafa806a124a9)
+++ BOOK/preface/arm/bookinfo.xml	(revision 193c88a3b3de32aafa97f685bc7fafa806a124a9)
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
+  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+  <!ENTITY % general-entities SYSTEM "../../general.ent">
+  %general-entities;
+]>
+
+<bookinfo>
+
+  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
+  href="../x86/bookinfo.xml"
+  xpointer="xpointer(/bookinfo/title)"/>
+
+  <subtitle>Version &version-arm;</subtitle>
+
+  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
+  href="../x86/bookinfo.xml"
+  xpointer="xpointer(/bookinfo/copyright)"/>
+
+  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
+  href="../x86/bookinfo.xml"
+  xpointer="xpointer(/bookinfo/legalnotice)"/>
+
+</bookinfo>
Index: BOOK/preface/common/audience.xml
===================================================================
--- BOOK/preface/common/audience.xml	(revision 193c88a3b3de32aafa97f685bc7fafa806a124a9)
+++ BOOK/preface/common/audience.xml	(revision 193c88a3b3de32aafa97f685bc7fafa806a124a9)
@@ -0,0 +1,83 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
+  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+  <!ENTITY % general-entities SYSTEM "../../general.ent">
+  %general-entities;
+]>
+
+<sect1 id="pre-audience">
+  <?dbhtml filename="audience.html"?>
+
+  <title>Audience</title>
+
+  <para>There are many reasons why somebody would want to read this book.
+  The principal reason is to install a Linux system 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 the existence of CLFS is to help people
+  understand how a Linux system works.  Building an CLFS system helps
+  demonstrate what makes Linux tick, and how things work together and
+  depend on each other. One of the best things this learning experience
+  provides is the ability to customize Linux to your own
+  tastes and needs.</para>
+
+  <para>A key benefit of CLFS is that it allows users to have more control
+  over their system without any reliance on a Linux implementation designed
+  by someone else.  With CLFS, <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 CLFS is the ability to create a very compact
+  Linux system. When installing a regular distribution, one is often forced
+  to include several programs which are probably never used. These programs
+  waste disk space or CPU cycles.  It is not difficult to build an CLFS Embedded
+  system of less than 10 megabytes (MB), which is substantially smaller
+  than the majority of existing installations.  Try that with a
+  regular distribution!</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. CLFS, on the other hand, does not give you a hamburger.
+  Rather, CLFS 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 CLFS with a
+  finished house. CLFS provides the skeletal plan of a house, but it is up
+  to you to build it. CLFS maintains the freedom to adjust plans throughout
+  the process, customizing it to the needs and preferences of the user.</para>
+
+  <para>Security is an additional advantage of a custom built Linux system.
+  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 Cross 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 shell prompt.
+  Consider your objective. If you wish to build a Linux system and learn
+  along the way, this book is your best choice.</para>
+
+  <para>There are too many good reasons to build your own CLFS system to
+  list them all here. This section is only the tip of the iceberg. As
+  you continue in your CLFS experience, you will find the power that
+  information and knowledge truly bring.</para>
+
+</sect1>
Index: BOOK/preface/common/dedication.xml
===================================================================
--- BOOK/preface/common/dedication.xml	(revision 193c88a3b3de32aafa97f685bc7fafa806a124a9)
+++ BOOK/preface/common/dedication.xml	(revision 193c88a3b3de32aafa97f685bc7fafa806a124a9)
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE dedication PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
+  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+  <!ENTITY % general-entities SYSTEM "../../general.ent">
+  %general-entities;
+]>
+
+<dedication>
+  <title>Dedication</title>
+  <para>This book is dedicated</para>
+</dedication>
Index: BOOK/preface/common/errata.xml
===================================================================
--- BOOK/preface/common/errata.xml	(revision 193c88a3b3de32aafa97f685bc7fafa806a124a9)
+++ BOOK/preface/common/errata.xml	(revision 193c88a3b3de32aafa97f685bc7fafa806a124a9)
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
+  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+  <!ENTITY % general-entities SYSTEM "../../general.ent">
+  %general-entities;
+]>
+
+<sect1 id="pre-errata">
+  <?dbhtml filename="errata.html"?>
+
+  <title>Errata</title>
+
+  <para>The software used to create a CLFS system is constantly being
+  updated and enhanced. Security warnings and bug fixes may become
+  available after the CLFS book has been released. Once a release of
+  the CLFS Embedded book is made, this page will provide a link to the
+  CLFS Embedded errata page.
+  <!--To check whether the
+  package versions or instructions in this release of CLFS need any
+  modifications to accommodate security vulnerabilities or other bug fixes,
+  please visit <ulink url="&errata;"/> before proceeding with your build.
+  You should note any changes shown and apply them to the relevant section
+  of the book as you progress with building the CLFS system.--></para>
+
+</sect1>
Index: BOOK/preface/common/foreword.xml
===================================================================
--- BOOK/preface/common/foreword.xml	(revision 193c88a3b3de32aafa97f685bc7fafa806a124a9)
+++ BOOK/preface/common/foreword.xml	(revision 193c88a3b3de32aafa97f685bc7fafa806a124a9)
@@ -0,0 +1,53 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
+  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+  <!ENTITY % general-entities SYSTEM "../../general.ent">
+  %general-entities;
+]>
+
+<sect1 id="pre-foreword">
+  <?dbhtml filename="foreword.html"?>
+
+  <title>Foreword</title>
+
+  <para>The Linux From Scratch Project has seen many changes in the
+  few years of its existence.  I personally became involved with the
+  project in 2000, around the time of the 3.x releases.  At that time,
+  the build process was to create static binaries with the host system,
+  then chroot and build the final binaries on top of the static ones.</para>
+
+  <para>Later came the use of the /static directory to hold the initial
+  static builds, keeping them separated from the final system, then
+  the PureLFS process developed by Ryan Oliver and Greg Schafer,
+  introducing a new toolchain build process that divorces even our initial
+  builds from the host.  Finally, LFS 6 bought Linux Kernel 2.6, the
+  udev dynamic device structure, sanitized kernel headers, and other
+  improvements to the Linux From Scratch system.</para>
+
+  <para>The one "flaw" in LFS is that it has always been based on an x86
+  class processor.  With the advent of the Athlon 64 and Intel EM64T
+  processors, the x86-only LFS is no longer ideal. Throughout this time,
+  Ryan Oliver developed and documented a process by which you could
+  build Linux for any system and from any system, by use of
+  cross-compilation techniques. Thus, the Cross-Compiled  LFS (CLFS) was
+  born.</para>
+
+  <para>CLFS Embedded follows the same guiding principles the LFS project has
+  always followed, e.g., knowing your system inside and out by virtue
+  of having built the system yourself.  Additionally, during a CLFS Embedded
+  build, you will learn advanced techniques such as cross-build toolchains,
+  and how to create a smaller footprint system supporting architectures
+  such as ARM and MIPS, in addition to x86.</para>
+
+  <para>We hope you enjoy building your own CLFS Embedded system, and the benefits
+  that come from a system tailored to your needs.</para>
+
+<literallayout>--
+Jim Gifford, CLFS Project Co-leader (Page Author)
+Jeremy Utley, CLFS 1.x Release Manager (Page Author)
+Ryan Oliver, CLFS Project Co-leader
+Joe Ciccone, Justin Knierim, Chris Staub, Matt Darcy, Ken Moffat,
+Maarten Lankhorst, Zack Winkles, Manuel Canales Esparcia,
+Nathan Coulson, and Andrew Bradford - CLFS Developers</literallayout>
+
+</sect1>
Index: BOOK/preface/common/hostreqs.xml
===================================================================
--- BOOK/preface/common/hostreqs.xml	(revision 193c88a3b3de32aafa97f685bc7fafa806a124a9)
+++ BOOK/preface/common/hostreqs.xml	(revision 193c88a3b3de32aafa97f685bc7fafa806a124a9)
@@ -0,0 +1,123 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
+  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+  <!ENTITY % general-entities SYSTEM "../../general.ent">
+  %general-entities;
+]>
+
+<sect1 id="pre-hostreqs">
+  <?dbhtml filename="hostreqs.html"?>
+
+  <title>Host System Requirements</title>
+
+    <para>You should be able to build a CLFS system from just about any
+    recent Linux distrubtion. Your host system should have the following
+    software with the minimum versions indicated. Also note that many
+    distributions will place software headers into separate packages, often in
+    the form of <quote>[package-name]-devel</quote> or
+    <quote>[package-name]-dev</quote>. Be sure to install those if
+    your distribution provides them.</para>
+
+  <itemizedlist spacing="compact">
+
+    <listitem>
+      <para><emphasis role="strong">Bash-4.0</emphasis></para>
+    </listitem>
+
+    <listitem>
+      <para><emphasis role="strong">Binutils-2.20</emphasis></para>
+    </listitem>
+
+    <listitem>
+      <para><emphasis role="strong">Bzip2-1.0.5</emphasis></para>
+    </listitem>
+
+    <listitem>
+      <para><emphasis role="strong">Coreutils-8.1</emphasis></para>
+    </listitem>
+
+    <listitem>
+      <para><emphasis role="strong">Diffutils-3.0</emphasis></para>
+    </listitem>
+
+    <listitem>
+      <para><emphasis role="strong">Findutils-4.4.0</emphasis></para>
+    </listitem>
+
+    <listitem>
+      <para><emphasis role="strong">Gawk-3.1</emphasis></para>
+    </listitem>
+
+    <listitem>
+      <para><emphasis role="strong">GCC-4.4</emphasis></para>
+    </listitem>
+
+    <listitem>
+      <para><emphasis role="strong">Glibc-2.11</emphasis></para>
+    </listitem>
+
+    <listitem>
+      <para><emphasis role="strong">Grep-2.6</emphasis></para>
+    </listitem>
+
+    <listitem>
+      <para><emphasis role="strong">Gzip-1.3</emphasis></para>
+    </listitem>
+
+    <listitem>
+      <para><emphasis role="strong">Make-3.81</emphasis></para>
+    </listitem>
+
+    <listitem>
+      <para><emphasis role="strong">Patch-2.6</emphasis></para>
+    </listitem>
+
+    <listitem>
+      <para><emphasis role="strong">Sed-4.2.1</emphasis></para>
+    </listitem>
+
+    <listitem>
+      <para><emphasis role="strong">Sudo-1.7.4p4</emphasis></para>
+    </listitem>
+
+    <listitem>
+      <para><emphasis role="strong">Tar-1.23</emphasis></para>
+    </listitem>
+
+    <listitem>
+      <para><emphasis role="strong">Texinfo-4.13</emphasis></para>
+    </listitem>
+
+  </itemizedlist>
+
+  <para>To see whether your host system has all the appropriate versions, run the following:</para>
+
+<screen role="nodump"><userinput>cat &gt; version-check.sh &lt;&lt; "EOF"
+<literal>#!/bin/bash
+
+# Simple script to list version numbers of critical development tools
+
+bash --version | head -n1 | cut -d" " -f2-4
+echo -n "Binutils: "; ld --version | head -n1 | cut -d" " -f3-
+bzip2 --version 2&gt;&amp;1 &lt; /dev/null | head -n1 | cut -d" " -f1,6-
+echo -n "Coreutils: "; chown --version | head -n1 | cut -d")" -f2
+diff --version | head -n1
+find --version | head -n1
+gawk --version | head -n1
+gcc --version | head -n1
+ldd $(which ${SHELL}) | grep libc.so | cut -d ' ' -f 3 | ${SHELL} | head -n 1 \
+| cut -d ' ' -f 1-10
+grep --version | head -n1
+gzip --version | head -n1
+make --version | head -n1
+patch --version | head -n1
+sed --version | head -n1
+sudo -V | head -n1
+tar --version | head -n1
+makeinfo --version | head -n1</literal>
+
+EOF
+
+bash version-check.sh</userinput></screen>
+
+</sect1>
Index: BOOK/preface/common/license.xml
===================================================================
--- BOOK/preface/common/license.xml	(revision 193c88a3b3de32aafa97f685bc7fafa806a124a9)
+++ BOOK/preface/common/license.xml	(revision 193c88a3b3de32aafa97f685bc7fafa806a124a9)
@@ -0,0 +1,189 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
+  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+  <!ENTITY % general-entities SYSTEM "../../general.ent">
+  %general-entities;
+]>
+
+<sect1 id="license" xreflabel="Open Publication License">
+  <?dbhtml dir="preface"?>
+  <?dbhtml filename="license.html"?>
+
+  <title>Open Publication License</title>
+  <bridgehead renderas="sect3">v1.0, 8 June 1999</bridgehead>
+
+
+  <bridgehead renderas="sect2">I. REQUIREMENTS ON BOTH UNMODIFIED AND
+  MODIFIED VERSIONS</bridgehead>
+
+  <para>The Open Publication works may be reproduced and distributed in
+  whole or in part, in any medium physical or electronic, provided that
+  the terms of this license are adhered to, and that this license or an
+  incorporation of it by reference (with any options elected by the
+  author(s) and/or publisher) is displayed in the reproduction.</para>
+
+  <para>Proper form for an incorporation by reference is as follows:</para>
+
+  <blockquote>
+    <para>Copyright &copy; &year; by each contributor.
+    This material may be distributed only subject to the terms and conditions
+    set forth in the Open Publication License, v1.0 or later (the latest
+    version is presently available at <ulink
+    url="http://www.opencontent.org/openpub/"/>).</para>
+  </blockquote>
+
+  <para>The reference must be immediately followed with any options elected
+  by the author(s) and/or publisher of the document (see section VI).</para>
+
+  <para>Commercial redistribution of Open Publication-licensed material
+  is permitted.</para>
+
+  <para>Any publication in standard (paper) book form shall require the
+  citation of the original publisher and author. The publisher and
+  author's names shall appear on all outer surfaces of the book. On all
+  outer surfaces of the book the original publisher's name shall be as
+  large as the bridgehead of the work and cited as possessive with respect
+  to the bridgehead.</para>
+
+
+  <bridgehead renderas="sect2">II. COPYRIGHT</bridgehead>
+
+  <para>The copyright to each Open Publication is owned by its
+  author(s) or designee.</para>
+
+  <bridgehead renderas="sect2">III. SCOPE OF LICENSE</bridgehead>
+
+  <para>The following license terms apply to all Open Publication works,
+  unless otherwise explicitly stated in the document.</para>
+
+  <para>Mere aggregation of Open Publication works or a portion of an
+  Open Publication work with other works or programs on the same media
+  shall not cause this license to apply to those other works. The
+  aggregate work shall contain a notice specifying the inclusion of the
+  Open Publication material and appropriate copyright notice.</para>
+
+  <para>SEVERABILITY. If any part of this license is found to be
+  unenforceable in any jurisdiction, the remaining portions of the
+  license remain in force.</para>
+
+  <para>NO WARRANTY. Open Publication works are licensed and provided
+  "as is" without warranty of any kind, express or implied, including,
+  but not limited to, the implied warranties of merchantability and
+  fitness for a particular purpose or a warranty of non-infringement.</para>
+
+
+  <bridgehead renderas="sect2">IV. REQUIREMENTS ON MODIFIED WORKS</bridgehead>
+
+  <para>All modified versions of documents covered by this license,
+  including translations, anthologies, compilations and partial documents,
+  must meet the following requirements:</para>
+
+  <orderedlist>
+    <listitem>
+      <para>The modified version must be labeled as such.</para>
+    </listitem>
+    <listitem>
+      <para>The person making the modifications must be identified and
+      the modifications dated.</para>
+    </listitem>
+    <listitem>
+      <para>Acknowledgement of the original author and publisher if
+      applicable must be retained according to normal academic citation
+      practices.</para>
+    </listitem>
+    <listitem>
+      <para>The location of the original unmodified document must be
+      identified.</para>
+    </listitem>
+    <listitem>
+      <para>The original author's (or authors') name(s) may not be used
+      to assert or imply endorsement of the resulting document without
+      the original author's (or authors') permission.</para>
+    </listitem>
+  </orderedlist>
+
+
+  <bridgehead renderas="sect2">V. GOOD-PRACTICE RECOMMENDATIONS</bridgehead>
+
+  <para>In addition to the requirements of this license, it is requested
+  from and strongly recommended of redistributors that:</para>
+
+  <orderedlist>
+    <listitem>
+      <para>If you are distributing Open Publication works on hardcopy
+      or CD-ROM, you provide email notification to the authors of your
+      intent to redistribute at least thirty days before your manuscript
+      or media freeze, to give the authors time to provide updated
+      documents. This notification should describe modifications, if any,
+      made to the document.</para>
+    </listitem>
+    <listitem>
+      <para>All substantive modifications (including deletions) be either
+      clearly marked up in the document or else described in an attachment
+      to the document.</para>
+    </listitem>
+    <listitem>
+      <para>Finally, while it is not mandatory under this license, it is
+      considered good form to offer a free copy of any hardcopy and CD-ROM
+      expression of an Open Publication-licensed work to its author(s).</para>
+    </listitem>
+  </orderedlist>
+
+
+  <bridgehead renderas="sect2">VI. LICENSE OPTIONS</bridgehead>
+
+  <para>The author(s) and/or publisher of an Open Publication-licensed
+  document may elect certain options by appending language to the reference
+  to or copy of the license. These options are considered part of the
+  license instance and must be included with the license (or its
+  incorporation by reference) in derived works.</para>
+
+  <para>A. To prohibit distribution of substantively modified versions
+  without the explicit permission of the author(s). "Substantive modification"
+  is defined as a change to the semantic content of the document, and
+  excludes mere changes in format or typographical corrections.</para>
+
+  <para>To accomplish this, add the phrase `Distribution of substantively
+  modified versions of this document is prohibited without the explicit
+  permission of the copyright holder.' to the license reference or copy.</para>
+
+  <para>B. To prohibit any publication of this work or derivative works in
+  whole or in part in standard (paper) book form for commercial purposes
+  is prohibited unless prior permission is obtained from the copyright
+  holder.</para>
+
+  <para>To accomplish this, add the phrase 'Distribution of the work or
+  derivative of the work in any standard (paper) book form is prohibited
+  unless prior permission is obtained from the copyright holder.' to the
+  license reference or copy.</para>
+
+
+  <bridgehead renderas="sect2">OPEN PUBLICATION POLICY APPENDIX</bridgehead>
+
+  <para>(This is not considered part of the license.)</para>
+
+  <para>Open Publication works are available in source format via the Open
+  Publication home page at <ulink url="http://works.opencontent.org/"/>.</para>
+
+  <para>Open Publication authors who want to include their own license on
+  Open Publication works may do so, as long as their terms are not more
+  restrictive than the Open Publication license.</para>
+
+  <para>If you have questions about the Open Publication License, please
+  contact <ulink url="mailto:dw@opencontent.org">David Wiley</ulink>, and/or the
+  <ulink url="mailto:opal@opencontent.org">Open Publication Authors'
+   List</ulink>, via email.</para>
+
+  <para>To <emphasis role="strong">subscribe</emphasis> to the Open Publication
+  Authors' List: Send E-mail to opal-request@opencontent.org with the word
+  "subscribe" in the body.</para>
+
+  <para>To <emphasis role="strong">post</emphasis> to the Open Publication
+  Authors' List: Send E-mail to opal@opencontent.org or simply reply to a
+  previous post.</para>
+
+  <para>To <emphasis role="strong">unsubscribe</emphasis> from the Open
+  Publication Authors' List: Send E-mail to opal-request@opencontent.org
+  with the word "unsubscribe" in the body.</para>
+
+</sect1>
Index: BOOK/preface/common/organization.xml
===================================================================
--- BOOK/preface/common/organization.xml	(revision 193c88a3b3de32aafa97f685bc7fafa806a124a9)
+++ BOOK/preface/common/organization.xml	(revision 193c88a3b3de32aafa97f685bc7fafa806a124a9)
@@ -0,0 +1,68 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
+  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+  <!ENTITY % general-entities SYSTEM "../../general.ent">
+  %general-entities;
+]>
+<sect1 id="pre-organization">
+  <?dbhtml filename="organization.html"?>
+
+  <title>Structure</title>
+
+  <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
+    Cross-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 including downloading the packages.</para>
+
+  </sect2>
+
+  <sect2>
+    <title>Part III - Make the Cross-Compile Tools</title>
+
+    <para>Part III shows you how to make a set of Cross-Compiler
+    tools. These tools can run on your host system but allow you to
+    build packages that will run on your target system.</para>
+
+  </sect2>
+
+  <sect2>
+    <title>Part IV - Building the CLFS System</title>
+
+    <para>Part IV shows you how to build the core CLFS system.  Compiling
+    and installing Buxybox and other required packages, making the system
+    bootable, setting up the bootscripts, and installing a bootloader.</para>
+
+  </sect2>
+
+  <sect2>
+    <title>Part V - Beyond CLFS Embedded</title>
+
+    <para>Part V provides instructions on optional packages that can be
+    installed to enhance your CLFS system.</para>
+
+  </sect2>
+
+  <sect2>
+    <title>Appendices</title>
+
+    <para>The appendices contain information that doesn't really fit anywhere
+    else in the book. Appendix A contains definitions of acronyms and
+    terms used in the book; Appendix B and C have information about package
+    dependencies and the the build order; Appendix D provides the Open
+    Publication License.</para>
+
+  </sect2>
+
+</sect1>
Index: BOOK/preface/common/prerequisites.xml
===================================================================
--- BOOK/preface/common/prerequisites.xml	(revision 193c88a3b3de32aafa97f685bc7fafa806a124a9)
+++ BOOK/preface/common/prerequisites.xml	(revision 193c88a3b3de32aafa97f685bc7fafa806a124a9)
@@ -0,0 +1,52 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
+  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+  <!ENTITY % general-entities SYSTEM "../../general.ent">
+  %general-entities;
+]>
+
+<sect1 id="pre-prerequisites">
+  <?dbhtml filename="prerequisites.html"?>
+
+  <title>Prerequisites</title>
+
+  <para>Building a CLFS system is not a simple task. It requires a certain
+  level of existing knowledge of Unix system administration in order to
+  resolve problems, and correctly execute the commands listed. In particular,
+  as an absolute minimum, the reader should already have the ability to use
+  the command line (shell) to copy or move files and directories, list
+  directory and file contents, and change the current directory. It is also
+  expected that the reader has a reasonable knowledge of using and installing
+  Linux software. A basic knowledge of the architectures being used in 
+  the Cross LFS process and the host operating systems in use is also
+  required.</para>
+
+  <para>Because the CLFS book assumes <emphasis>at least</emphasis> this basic
+  level of skill, the various CLFS support forums are unlikely to be able to
+  provide you with much assistance. Your questions regarding such basic knowledge
+  will likely go unanswered, or you will be referred to the CLFS essential
+  pre-reading list.</para>
+
+  <para>Before building a CLFS 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 Essential Pre-Reading Hint
+      <ulink url="&hints-root;essential_prereading.txt"/></para>
+
+      <para>This is a 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 CLFS should have an
+      understanding of many of the topics in this hint.</para>
+    </listitem>
+  </itemizedlist>
+
+</sect1>
Index: BOOK/preface/common/typography.xml
===================================================================
--- BOOK/preface/common/typography.xml	(revision 193c88a3b3de32aafa97f685bc7fafa806a124a9)
+++ BOOK/preface/common/typography.xml	(revision 193c88a3b3de32aafa97f685bc7fafa806a124a9)
@@ -0,0 +1,74 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
+  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+  <!ENTITY % general-entities SYSTEM "../../general.ent">
+  %general-entities;
+]>
+
+<sect1 id="pre-typography">
+  <?dbhtml filename="typography.html"?>
+
+  <title>Typography</title>
+
+  <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 role="nodump"><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/clfs/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.
+  Its main purpose is to emphasize important points or items.</para>
+
+  <para><ulink url="&clfs-root;"/></para>
+
+  <para>This format is used for hyperlinks, both within the CLFS
+  community and to external pages. It includes HOWTOs, download locations,
+  and websites.</para>
+
+<screen role="nodump"><userinput>cat &gt; ${CLFS}/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>${CLFS}/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 or copied-and-pasted.</para>
+
+  <para><filename>passwd(5)</filename></para>
+
+  <para>This format is used to refer to a specific manual page (hereinafter
+  referred to simply as a <quote>man</quote> page). The number inside
+  parentheses indicates a specific section inside of <command>man</command>.
+  For example, <command>passwd</command> has two man pages.
+  <command>man passwd</command> will print the first man page it finds
+  that matches <quote>passwd</quote>, which will be
+  <filename>/usr/share/man/man1/passwd.1</filename>. For this example,
+  you will need to run <command>man 5 passwd</command> in order to read
+  the specific page being referred to. It should be noted that most man
+  pages do not have duplicate page names in different sections. Therefore,
+  <command>man <replaceable>[program name]</replaceable></command> is
+  generally sufficient.</para>
+
+</sect1>
Index: BOOK/preface/mips/bookinfo.xml
===================================================================
--- BOOK/preface/mips/bookinfo.xml	(revision 193c88a3b3de32aafa97f685bc7fafa806a124a9)
+++ BOOK/preface/mips/bookinfo.xml	(revision 193c88a3b3de32aafa97f685bc7fafa806a124a9)
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
+  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+  <!ENTITY % general-entities SYSTEM "../../general.ent">
+  %general-entities;
+]>
+
+<bookinfo>
+
+  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
+  href="../x86/bookinfo.xml"
+  xpointer="xpointer(/bookinfo/title)"/>
+
+  <subtitle>Version &version-mips;</subtitle>
+
+  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
+  href="../x86/bookinfo.xml"
+  xpointer="xpointer(/bookinfo/copyright)"/>
+
+  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
+  href="../x86/bookinfo.xml"
+  xpointer="xpointer(/bookinfo/legalnotice)"/>
+
+</bookinfo>
Index: BOOK/preface/preface.xml
===================================================================
--- BOOK/preface/preface.xml	(revision 193c88a3b3de32aafa97f685bc7fafa806a124a9)
+++ BOOK/preface/preface.xml	(revision 193c88a3b3de32aafa97f685bc7fafa806a124a9)
@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE preface PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
+  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+  <!ENTITY % general-entities SYSTEM "../general.ent">
+  %general-entities;
+]>
+
+<preface id="preface">
+  <?dbhtml dir="preface"?>
+  <?dbhtml filename="preface.html"?>
+
+  <title>Preface</title>
+
+  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/foreword.xml"/>
+  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/audience.xml"/>
+  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/prerequisites.xml"/>
+  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/hostreqs.xml"/>
+  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/typography.xml"/>
+  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/organization.xml"/>
+  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/license.xml"/>
+  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/errata.xml"/>
+
+</preface>
Index: BOOK/preface/x86/bookinfo.xml
===================================================================
--- BOOK/preface/x86/bookinfo.xml	(revision 193c88a3b3de32aafa97f685bc7fafa806a124a9)
+++ BOOK/preface/x86/bookinfo.xml	(revision 193c88a3b3de32aafa97f685bc7fafa806a124a9)
@@ -0,0 +1,38 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
+  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+  <!ENTITY % general-entities SYSTEM "../../general.ent">
+  %general-entities;
+]>
+
+<bookinfo>
+
+  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
+  href="../../index.xml"
+  xpointer="xpointer(/bookinfo/title)"/>
+
+  <subtitle>Version &version-x86;</subtitle>
+
+  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
+  href="../../index.xml"
+  xpointer="xpointer(/bookinfo/copyright)"/>
+
+  <legalnotice>
+    <para>Copyright &copy; 2005-&year;, Joe Ciccone, Jim Gifford, Maarten Lankhorst, &amp; Ryan Oliver</para>
+
+    <para>All rights reserved.</para>
+
+    <para>This material may be distributed only subject to the terms and
+    conditions set forth in the <xref linkend="license"/> v1.0 or later
+    (the latest version is presently available at <ulink
+    url="http://www.opencontent.org/openpub/"/>).</para>
+
+    <!-- Modifications and limitations to the OPL (see section VI)
+    can be place here, if needed. -->
+
+    <para><trademark class='registered'>Linux</trademark> is a registered
+    trademark of Linus Torvalds.</para>
+
+  </legalnotice>
+
+</bookinfo>
Index: OK/prologue/arm/bookinfo.xml
===================================================================
--- BOOK/prologue/arm/bookinfo.xml	(revision 3aed10f5cd26989641844df4b6bbb48db8d9e8dc)
+++ 	(revision )
@@ -1,24 +1,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../../general.ent">
-  %general-entities;
-]>
-
-<bookinfo>
-
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-  href="../x86/bookinfo.xml"
-  xpointer="xpointer(/bookinfo/title)"/>
-
-  <subtitle>Version &version-arm;</subtitle>
-
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-  href="../x86/bookinfo.xml"
-  xpointer="xpointer(/bookinfo/copyright)"/>
-
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-  href="../x86/bookinfo.xml"
-  xpointer="xpointer(/bookinfo/legalnotice)"/>
-
-</bookinfo>
Index: OK/prologue/common/audience.xml
===================================================================
--- BOOK/prologue/common/audience.xml	(revision 3aed10f5cd26989641844df4b6bbb48db8d9e8dc)
+++ 	(revision )
@@ -1,83 +1,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="pre-audience">
-  <?dbhtml filename="audience.html"?>
-
-  <title>Audience</title>
-
-  <para>There are many reasons why somebody would want to read this book.
-  The principal reason is to install a Linux system 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 the existence of CLFS is to help people
-  understand how a Linux system works.  Building an CLFS system helps
-  demonstrate what makes Linux tick, and how things work together and
-  depend on each other. One of the best things this learning experience
-  provides is the ability to customize Linux to your own
-  tastes and needs.</para>
-
-  <para>A key benefit of CLFS is that it allows users to have more control
-  over their system without any reliance on a Linux implementation designed
-  by someone else.  With CLFS, <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 CLFS is the ability to create a very compact
-  Linux system. When installing a regular distribution, one is often forced
-  to include several programs which are probably never used. These programs
-  waste disk space or CPU cycles.  It is not difficult to build an CLFS Embedded
-  system of less than 10 megabytes (MB), which is substantially smaller
-  than the majority of existing installations.  Try that with a
-  regular distribution!</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. CLFS, on the other hand, does not give you a hamburger.
-  Rather, CLFS 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 CLFS with a
-  finished house. CLFS provides the skeletal plan of a house, but it is up
-  to you to build it. CLFS maintains the freedom to adjust plans throughout
-  the process, customizing it to the needs and preferences of the user.</para>
-
-  <para>Security is an additional advantage of a custom built Linux system.
-  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 Cross 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 shell prompt.
-  Consider your objective. If you wish to build a Linux system and learn
-  along the way, this book is your best choice.</para>
-
-  <para>There are too many good reasons to build your own CLFS system to
-  list them all here. This section is only the tip of the iceberg. As
-  you continue in your CLFS experience, you will find the power that
-  information and knowledge truly bring.</para>
-
-</sect1>
Index: OK/prologue/common/dedication.xml
===================================================================
--- BOOK/prologue/common/dedication.xml	(revision 3aed10f5cd26989641844df4b6bbb48db8d9e8dc)
+++ 	(revision )
@@ -1,11 +1,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE dedication PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../../general.ent">
-  %general-entities;
-]>
-
-<dedication>
-  <title>Dedication</title>
-  <para>This book is dedicated</para>
-</dedication>
Index: OK/prologue/common/errata.xml
===================================================================
--- BOOK/prologue/common/errata.xml	(revision 3aed10f5cd26989641844df4b6bbb48db8d9e8dc)
+++ 	(revision )
@@ -1,25 +1,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="pre-errata">
-  <?dbhtml filename="errata.html"?>
-
-  <title>Errata</title>
-
-  <para>The software used to create a CLFS system is constantly being
-  updated and enhanced. Security warnings and bug fixes may become
-  available after the CLFS book has been released. Once a release of
-  the CLFS Embedded book is made, this page will provide a link to the
-  CLFS Embedded errata page.
-  <!--To check whether the
-  package versions or instructions in this release of CLFS need any
-  modifications to accommodate security vulnerabilities or other bug fixes,
-  please visit <ulink url="&errata;"/> before proceeding with your build.
-  You should note any changes shown and apply them to the relevant section
-  of the book as you progress with building the CLFS system.--></para>
-
-</sect1>
Index: OK/prologue/common/foreword.xml
===================================================================
--- BOOK/prologue/common/foreword.xml	(revision 3aed10f5cd26989641844df4b6bbb48db8d9e8dc)
+++ 	(revision )
@@ -1,53 +1,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="pre-foreword">
-  <?dbhtml filename="foreword.html"?>
-
-  <title>Foreword</title>
-
-  <para>The Linux From Scratch Project has seen many changes in the
-  few years of its existence.  I personally became involved with the
-  project in 2000, around the time of the 3.x releases.  At that time,
-  the build process was to create static binaries with the host system,
-  then chroot and build the final binaries on top of the static ones.</para>
-
-  <para>Later came the use of the /static directory to hold the initial
-  static builds, keeping them separated from the final system, then
-  the PureLFS process developed by Ryan Oliver and Greg Schafer,
-  introducing a new toolchain build process that divorces even our initial
-  builds from the host.  Finally, LFS 6 bought Linux Kernel 2.6, the
-  udev dynamic device structure, sanitized kernel headers, and other
-  improvements to the Linux From Scratch system.</para>
-
-  <para>The one "flaw" in LFS is that it has always been based on an x86
-  class processor.  With the advent of the Athlon 64 and Intel EM64T
-  processors, the x86-only LFS is no longer ideal. Throughout this time,
-  Ryan Oliver developed and documented a process by which you could
-  build Linux for any system and from any system, by use of
-  cross-compilation techniques. Thus, the Cross-Compiled  LFS (CLFS) was
-  born.</para>
-
-  <para>CLFS Embedded follows the same guiding principles the LFS project has
-  always followed, e.g., knowing your system inside and out by virtue
-  of having built the system yourself.  Additionally, during a CLFS Embedded
-  build, you will learn advanced techniques such as cross-build toolchains,
-  and how to create a smaller footprint system supporting architectures
-  such as ARM and MIPS, in addition to x86.</para>
-
-  <para>We hope you enjoy building your own CLFS Embedded system, and the benefits
-  that come from a system tailored to your needs.</para>
-
-<literallayout>--
-Jim Gifford, CLFS Project Co-leader (Page Author)
-Jeremy Utley, CLFS 1.x Release Manager (Page Author)
-Ryan Oliver, CLFS Project Co-leader
-Joe Ciccone, Justin Knierim, Chris Staub, Matt Darcy, Ken Moffat,
-Maarten Lankhorst, Zack Winkles, Manuel Canales Esparcia,
-Nathan Coulson, and Andrew Bradford - CLFS Developers</literallayout>
-
-</sect1>
Index: OK/prologue/common/hostreqs.xml
===================================================================
--- BOOK/prologue/common/hostreqs.xml	(revision 3aed10f5cd26989641844df4b6bbb48db8d9e8dc)
+++ 	(revision )
@@ -1,123 +1,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="pre-hostreqs">
-  <?dbhtml filename="hostreqs.html"?>
-
-  <title>Host System Requirements</title>
-
-    <para>You should be able to build a CLFS system from just about any
-    recent Linux distrubtion. Your host system should have the following
-    software with the minimum versions indicated. Also note that many
-    distributions will place software headers into separate packages, often in
-    the form of <quote>[package-name]-devel</quote> or
-    <quote>[package-name]-dev</quote>. Be sure to install those if
-    your distribution provides them.</para>
-
-  <itemizedlist spacing="compact">
-
-    <listitem>
-      <para><emphasis role="strong">Bash-4.0</emphasis></para>
-    </listitem>
-
-    <listitem>
-      <para><emphasis role="strong">Binutils-2.20</emphasis></para>
-    </listitem>
-
-    <listitem>
-      <para><emphasis role="strong">Bzip2-1.0.5</emphasis></para>
-    </listitem>
-
-    <listitem>
-      <para><emphasis role="strong">Coreutils-8.1</emphasis></para>
-    </listitem>
-
-    <listitem>
-      <para><emphasis role="strong">Diffutils-3.0</emphasis></para>
-    </listitem>
-
-    <listitem>
-      <para><emphasis role="strong">Findutils-4.4.0</emphasis></para>
-    </listitem>
-
-    <listitem>
-      <para><emphasis role="strong">Gawk-3.1</emphasis></para>
-    </listitem>
-
-    <listitem>
-      <para><emphasis role="strong">GCC-4.4</emphasis></para>
-    </listitem>
-
-    <listitem>
-      <para><emphasis role="strong">Glibc-2.11</emphasis></para>
-    </listitem>
-
-    <listitem>
-      <para><emphasis role="strong">Grep-2.6</emphasis></para>
-    </listitem>
-
-    <listitem>
-      <para><emphasis role="strong">Gzip-1.3</emphasis></para>
-    </listitem>
-
-    <listitem>
-      <para><emphasis role="strong">Make-3.81</emphasis></para>
-    </listitem>
-
-    <listitem>
-      <para><emphasis role="strong">Patch-2.6</emphasis></para>
-    </listitem>
-
-    <listitem>
-      <para><emphasis role="strong">Sed-4.2.1</emphasis></para>
-    </listitem>
-
-    <listitem>
-      <para><emphasis role="strong">Sudo-1.7.4p4</emphasis></para>
-    </listitem>
-
-    <listitem>
-      <para><emphasis role="strong">Tar-1.23</emphasis></para>
-    </listitem>
-
-    <listitem>
-      <para><emphasis role="strong">Texinfo-4.13</emphasis></para>
-    </listitem>
-
-  </itemizedlist>
-
-  <para>To see whether your host system has all the appropriate versions, run the following:</para>
-
-<screen role="nodump"><userinput>cat &gt; version-check.sh &lt;&lt; "EOF"
-<literal>#!/bin/bash
-
-# Simple script to list version numbers of critical development tools
-
-bash --version | head -n1 | cut -d" " -f2-4
-echo -n "Binutils: "; ld --version | head -n1 | cut -d" " -f3-
-bzip2 --version 2&gt;&amp;1 &lt; /dev/null | head -n1 | cut -d" " -f1,6-
-echo -n "Coreutils: "; chown --version | head -n1 | cut -d")" -f2
-diff --version | head -n1
-find --version | head -n1
-gawk --version | head -n1
-gcc --version | head -n1
-ldd $(which ${SHELL}) | grep libc.so | cut -d ' ' -f 3 | ${SHELL} | head -n 1 \
-| cut -d ' ' -f 1-10
-grep --version | head -n1
-gzip --version | head -n1
-make --version | head -n1
-patch --version | head -n1
-sed --version | head -n1
-sudo -V | head -n1
-tar --version | head -n1
-makeinfo --version | head -n1</literal>
-
-EOF
-
-bash version-check.sh</userinput></screen>
-
-</sect1>
Index: OK/prologue/common/license.xml
===================================================================
--- BOOK/prologue/common/license.xml	(revision 3aed10f5cd26989641844df4b6bbb48db8d9e8dc)
+++ 	(revision )
@@ -1,189 +1,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="license" xreflabel="Open Publication License">
-  <?dbhtml dir="prologue"?>
-  <?dbhtml filename="license.html"?>
-
-  <title>Open Publication License</title>
-  <bridgehead renderas="sect3">v1.0, 8 June 1999</bridgehead>
-
-
-  <bridgehead renderas="sect2">I. REQUIREMENTS ON BOTH UNMODIFIED AND
-  MODIFIED VERSIONS</bridgehead>
-
-  <para>The Open Publication works may be reproduced and distributed in
-  whole or in part, in any medium physical or electronic, provided that
-  the terms of this license are adhered to, and that this license or an
-  incorporation of it by reference (with any options elected by the
-  author(s) and/or publisher) is displayed in the reproduction.</para>
-
-  <para>Proper form for an incorporation by reference is as follows:</para>
-
-  <blockquote>
-    <para>Copyright &copy; &year; by each contributor.
-    This material may be distributed only subject to the terms and conditions
-    set forth in the Open Publication License, v1.0 or later (the latest
-    version is presently available at <ulink
-    url="http://www.opencontent.org/openpub/"/>).</para>
-  </blockquote>
-
-  <para>The reference must be immediately followed with any options elected
-  by the author(s) and/or publisher of the document (see section VI).</para>
-
-  <para>Commercial redistribution of Open Publication-licensed material
-  is permitted.</para>
-
-  <para>Any publication in standard (paper) book form shall require the
-  citation of the original publisher and author. The publisher and
-  author's names shall appear on all outer surfaces of the book. On all
-  outer surfaces of the book the original publisher's name shall be as
-  large as the bridgehead of the work and cited as possessive with respect
-  to the bridgehead.</para>
-
-
-  <bridgehead renderas="sect2">II. COPYRIGHT</bridgehead>
-
-  <para>The copyright to each Open Publication is owned by its
-  author(s) or designee.</para>
-
-  <bridgehead renderas="sect2">III. SCOPE OF LICENSE</bridgehead>
-
-  <para>The following license terms apply to all Open Publication works,
-  unless otherwise explicitly stated in the document.</para>
-
-  <para>Mere aggregation of Open Publication works or a portion of an
-  Open Publication work with other works or programs on the same media
-  shall not cause this license to apply to those other works. The
-  aggregate work shall contain a notice specifying the inclusion of the
-  Open Publication material and appropriate copyright notice.</para>
-
-  <para>SEVERABILITY. If any part of this license is found to be
-  unenforceable in any jurisdiction, the remaining portions of the
-  license remain in force.</para>
-
-  <para>NO WARRANTY. Open Publication works are licensed and provided
-  "as is" without warranty of any kind, express or implied, including,
-  but not limited to, the implied warranties of merchantability and
-  fitness for a particular purpose or a warranty of non-infringement.</para>
-
-
-  <bridgehead renderas="sect2">IV. REQUIREMENTS ON MODIFIED WORKS</bridgehead>
-
-  <para>All modified versions of documents covered by this license,
-  including translations, anthologies, compilations and partial documents,
-  must meet the following requirements:</para>
-
-  <orderedlist>
-    <listitem>
-      <para>The modified version must be labeled as such.</para>
-    </listitem>
-    <listitem>
-      <para>The person making the modifications must be identified and
-      the modifications dated.</para>
-    </listitem>
-    <listitem>
-      <para>Acknowledgement of the original author and publisher if
-      applicable must be retained according to normal academic citation
-      practices.</para>
-    </listitem>
-    <listitem>
-      <para>The location of the original unmodified document must be
-      identified.</para>
-    </listitem>
-    <listitem>
-      <para>The original author's (or authors') name(s) may not be used
-      to assert or imply endorsement of the resulting document without
-      the original author's (or authors') permission.</para>
-    </listitem>
-  </orderedlist>
-
-
-  <bridgehead renderas="sect2">V. GOOD-PRACTICE RECOMMENDATIONS</bridgehead>
-
-  <para>In addition to the requirements of this license, it is requested
-  from and strongly recommended of redistributors that:</para>
-
-  <orderedlist>
-    <listitem>
-      <para>If you are distributing Open Publication works on hardcopy
-      or CD-ROM, you provide email notification to the authors of your
-      intent to redistribute at least thirty days before your manuscript
-      or media freeze, to give the authors time to provide updated
-      documents. This notification should describe modifications, if any,
-      made to the document.</para>
-    </listitem>
-    <listitem>
-      <para>All substantive modifications (including deletions) be either
-      clearly marked up in the document or else described in an attachment
-      to the document.</para>
-    </listitem>
-    <listitem>
-      <para>Finally, while it is not mandatory under this license, it is
-      considered good form to offer a free copy of any hardcopy and CD-ROM
-      expression of an Open Publication-licensed work to its author(s).</para>
-    </listitem>
-  </orderedlist>
-
-
-  <bridgehead renderas="sect2">VI. LICENSE OPTIONS</bridgehead>
-
-  <para>The author(s) and/or publisher of an Open Publication-licensed
-  document may elect certain options by appending language to the reference
-  to or copy of the license. These options are considered part of the
-  license instance and must be included with the license (or its
-  incorporation by reference) in derived works.</para>
-
-  <para>A. To prohibit distribution of substantively modified versions
-  without the explicit permission of the author(s). "Substantive modification"
-  is defined as a change to the semantic content of the document, and
-  excludes mere changes in format or typographical corrections.</para>
-
-  <para>To accomplish this, add the phrase `Distribution of substantively
-  modified versions of this document is prohibited without the explicit
-  permission of the copyright holder.' to the license reference or copy.</para>
-
-  <para>B. To prohibit any publication of this work or derivative works in
-  whole or in part in standard (paper) book form for commercial purposes
-  is prohibited unless prior permission is obtained from the copyright
-  holder.</para>
-
-  <para>To accomplish this, add the phrase 'Distribution of the work or
-  derivative of the work in any standard (paper) book form is prohibited
-  unless prior permission is obtained from the copyright holder.' to the
-  license reference or copy.</para>
-
-
-  <bridgehead renderas="sect2">OPEN PUBLICATION POLICY APPENDIX</bridgehead>
-
-  <para>(This is not considered part of the license.)</para>
-
-  <para>Open Publication works are available in source format via the Open
-  Publication home page at <ulink url="http://works.opencontent.org/"/>.</para>
-
-  <para>Open Publication authors who want to include their own license on
-  Open Publication works may do so, as long as their terms are not more
-  restrictive than the Open Publication license.</para>
-
-  <para>If you have questions about the Open Publication License, please
-  contact <ulink url="mailto:dw@opencontent.org">David Wiley</ulink>, and/or the
-  <ulink url="mailto:opal@opencontent.org">Open Publication Authors'
-   List</ulink>, via email.</para>
-
-  <para>To <emphasis role="strong">subscribe</emphasis> to the Open Publication
-  Authors' List: Send E-mail to opal-request@opencontent.org with the word
-  "subscribe" in the body.</para>
-
-  <para>To <emphasis role="strong">post</emphasis> to the Open Publication
-  Authors' List: Send E-mail to opal@opencontent.org or simply reply to a
-  previous post.</para>
-
-  <para>To <emphasis role="strong">unsubscribe</emphasis> from the Open
-  Publication Authors' List: Send E-mail to opal-request@opencontent.org
-  with the word "unsubscribe" in the body.</para>
-
-</sect1>
Index: OK/prologue/common/organization.xml
===================================================================
--- BOOK/prologue/common/organization.xml	(revision 3aed10f5cd26989641844df4b6bbb48db8d9e8dc)
+++ 	(revision )
@@ -1,68 +1,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../../general.ent">
-  %general-entities;
-]>
-<sect1 id="pre-organization">
-  <?dbhtml filename="organization.html"?>
-
-  <title>Structure</title>
-
-  <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
-    Cross-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 including downloading the packages.</para>
-
-  </sect2>
-
-  <sect2>
-    <title>Part III - Make the Cross-Compile Tools</title>
-
-    <para>Part III shows you how to make a set of Cross-Compiler
-    tools. These tools can run on your host system but allow you to
-    build packages that will run on your target system.</para>
-
-  </sect2>
-
-  <sect2>
-    <title>Part IV - Building the CLFS System</title>
-
-    <para>Part IV shows you how to build the core CLFS system.  Compiling
-    and installing Buxybox and other required packages, making the system
-    bootable, setting up the bootscripts, and installing a bootloader.</para>
-
-  </sect2>
-
-  <sect2>
-    <title>Part V - Beyond CLFS Embedded</title>
-
-    <para>Part V provides instructions on optional packages that can be
-    installed to enhance your CLFS system.</para>
-
-  </sect2>
-
-  <sect2>
-    <title>Appendices</title>
-
-    <para>The appendices contain information that doesn't really fit anywhere
-    else in the book. Appendix A contains definitions of acronyms and
-    terms used in the book; Appendix B and C have information about package
-    dependencies and the the build order; Appendix D provides the Open
-    Publication License.</para>
-
-  </sect2>
-
-</sect1>
Index: OK/prologue/common/prerequisites.xml
===================================================================
--- BOOK/prologue/common/prerequisites.xml	(revision 3aed10f5cd26989641844df4b6bbb48db8d9e8dc)
+++ 	(revision )
@@ -1,52 +1,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="pre-prerequisites">
-  <?dbhtml filename="prerequisites.html"?>
-
-  <title>Prerequisites</title>
-
-  <para>Building a CLFS system is not a simple task. It requires a certain
-  level of existing knowledge of Unix system administration in order to
-  resolve problems, and correctly execute the commands listed. In particular,
-  as an absolute minimum, the reader should already have the ability to use
-  the command line (shell) to copy or move files and directories, list
-  directory and file contents, and change the current directory. It is also
-  expected that the reader has a reasonable knowledge of using and installing
-  Linux software. A basic knowledge of the architectures being used in 
-  the Cross LFS process and the host operating systems in use is also
-  required.</para>
-
-  <para>Because the CLFS book assumes <emphasis>at least</emphasis> this basic
-  level of skill, the various CLFS support forums are unlikely to be able to
-  provide you with much assistance. Your questions regarding such basic knowledge
-  will likely go unanswered, or you will be referred to the CLFS essential
-  pre-reading list.</para>
-
-  <para>Before building a CLFS 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 Essential Pre-Reading Hint
-      <ulink url="&hints-root;essential_prereading.txt"/></para>
-
-      <para>This is a 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 CLFS should have an
-      understanding of many of the topics in this hint.</para>
-    </listitem>
-  </itemizedlist>
-
-</sect1>
Index: OK/prologue/common/typography.xml
===================================================================
--- BOOK/prologue/common/typography.xml	(revision 3aed10f5cd26989641844df4b6bbb48db8d9e8dc)
+++ 	(revision )
@@ -1,74 +1,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="pre-typography">
-  <?dbhtml filename="typography.html"?>
-
-  <title>Typography</title>
-
-  <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 role="nodump"><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/clfs/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.
-  Its main purpose is to emphasize important points or items.</para>
-
-  <para><ulink url="&clfs-root;"/></para>
-
-  <para>This format is used for hyperlinks, both within the CLFS
-  community and to external pages. It includes HOWTOs, download locations,
-  and websites.</para>
-
-<screen role="nodump"><userinput>cat &gt; ${CLFS}/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>${CLFS}/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 or copied-and-pasted.</para>
-
-  <para><filename>passwd(5)</filename></para>
-
-  <para>This format is used to refer to a specific manual page (hereinafter
-  referred to simply as a <quote>man</quote> page). The number inside
-  parentheses indicates a specific section inside of <command>man</command>.
-  For example, <command>passwd</command> has two man pages.
-  <command>man passwd</command> will print the first man page it finds
-  that matches <quote>passwd</quote>, which will be
-  <filename>/usr/share/man/man1/passwd.1</filename>. For this example,
-  you will need to run <command>man 5 passwd</command> in order to read
-  the specific page being referred to. It should be noted that most man
-  pages do not have duplicate page names in different sections. Therefore,
-  <command>man <replaceable>[program name]</replaceable></command> is
-  generally sufficient.</para>
-
-</sect1>
Index: OK/prologue/mips/bookinfo.xml
===================================================================
--- BOOK/prologue/mips/bookinfo.xml	(revision 3aed10f5cd26989641844df4b6bbb48db8d9e8dc)
+++ 	(revision )
@@ -1,24 +1,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../../general.ent">
-  %general-entities;
-]>
-
-<bookinfo>
-
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-  href="../x86/bookinfo.xml"
-  xpointer="xpointer(/bookinfo/title)"/>
-
-  <subtitle>Version &version-mips;</subtitle>
-
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-  href="../x86/bookinfo.xml"
-  xpointer="xpointer(/bookinfo/copyright)"/>
-
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-  href="../x86/bookinfo.xml"
-  xpointer="xpointer(/bookinfo/legalnotice)"/>
-
-</bookinfo>
Index: OK/prologue/preface.xml
===================================================================
--- BOOK/prologue/preface.xml	(revision 3aed10f5cd26989641844df4b6bbb48db8d9e8dc)
+++ 	(revision )
@@ -1,23 +1,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE preface PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<preface id="preface">
-  <?dbhtml dir="prologue"?>
-  <?dbhtml filename="preface.html"?>
-
-  <title>Preface</title>
-
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/foreword.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/audience.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/prerequisites.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/hostreqs.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/typography.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/organization.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/license.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/errata.xml"/>
-
-</preface>
Index: OK/prologue/x86/bookinfo.xml
===================================================================
--- BOOK/prologue/x86/bookinfo.xml	(revision 3aed10f5cd26989641844df4b6bbb48db8d9e8dc)
+++ 	(revision )
@@ -1,38 +1,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../../general.ent">
-  %general-entities;
-]>
-
-<bookinfo>
-
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-  href="../../index.xml"
-  xpointer="xpointer(/bookinfo/title)"/>
-
-  <subtitle>Version &version-x86;</subtitle>
-
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-  href="../../index.xml"
-  xpointer="xpointer(/bookinfo/copyright)"/>
-
-  <legalnotice>
-    <para>Copyright &copy; 2005-&year;, Joe Ciccone, Jim Gifford, Maarten Lankhorst, &amp; Ryan Oliver</para>
-
-    <para>All rights reserved.</para>
-
-    <para>This material may be distributed only subject to the terms and
-    conditions set forth in the <xref linkend="license"/> v1.0 or later
-    (the latest version is presently available at <ulink
-    url="http://www.opencontent.org/openpub/"/>).</para>
-
-    <!-- Modifications and limitations to the OPL (see section VI)
-    can be place here, if needed. -->
-
-    <para><trademark class='registered'>Linux</trademark> is a registered
-    trademark of Linus Torvalds.</para>
-
-  </legalnotice>
-
-</bookinfo>
Index: BOOK/x86-index.xml
===================================================================
--- BOOK/x86-index.xml	(revision 3aed10f5cd26989641844df4b6bbb48db8d9e8dc)
+++ BOOK/x86-index.xml	(revision 193c88a3b3de32aafa97f685bc7fafa806a124a9)
@@ -8,6 +8,6 @@
 <book>
 
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="prologue/x86/bookinfo.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="prologue/preface.xml"/>
+  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="preface/x86/bookinfo.xml"/>
+  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="preface/preface.xml"/>
 
   <part id="part1">
