diff --git a/prologue/acknowledgments.xml b/prologue/acknowledgments.xml
index 016b40048..7522d77e9 100644
--- a/prologue/acknowledgments.xml
+++ b/prologue/acknowledgments.xml
@@ -7,109 +7,86 @@
Acknowledgments
-We would like to thank the following people and organizations for their
-contributions to the Linux From Scratch Project.
+We would like to thank the following people and organizations
+for their contributions to the Linux From Scratch Project.
-
-Current Project Team Members
+ Current Project Team Members
Gerard
-Beekmans <gerard@linuxfromscratch.org> -- Linux-From-Scratch
-initiator, LFS Project organizer.
+Beekmans <gerard@linuxfromscratch.org> -- Linux From
+Scratch initiator, LFS Project organizer.
-Matthew
-Burgess <matthew@linuxfromscratch.org> -- LFS Project Co-Leader,
-LFS General Package maintainer, LFS Book editor.
+Matthew Burgess
+<matthew@linuxfromscratch.org> -- LFS Project Co-Leader, LFS
+General Package maintainer, LFS Technical Writer.
Craig
-Colton <meerkats@bellsouth.net> -- LFS, ALFS, BLFS and Hints
-Project logo creator.
+Colton <meerkats@bellsouth.net> -- LFS, Automated Linux
+From Scratch (ALFS), Beyond Linux From Scratch (BLFS) and hints
+project logo creator.
Nathan
-Coulson <nathan@linuxfromscratch.org> -- LFS-Bootscripts
+Coulson <nathan@linuxfromscratch.org> -- LFS Bootscripts
maintainer.
Jeroen
-Coumans <jeroen@linuxfromscratch.org> -- Website developer, FAQ
+Coumans <jeroen@linuxfromscratch.org> -- Website
+developer, Frequently Asked Questions (FAQ)
maintainer.
Bruce
-Dubbs <bdubbs@linuxfromscratch.org> -- LFS Quality Assurance Team
-leader, BLFS Book editor.
+Dubbs <bdubbs@linuxfromscratch.org> -- LFS Quality
+Assurance (QA) Team leader, BLFS Book editor.
Manuel
-Canales Esparcia <manuel@linuxfromscratch.org> -- LFS Book
-Editor (XML).
+Canales Esparcia <manuel@linuxfromscratch.org> -- LFS
+XML/XSL Maintainer.
-Alex
-Groenewoud <alex@linuxfromscratch.org> -- LFS Book
-editor.
-
-Mark
-Hymers <markh@linuxfromscratch.org> -- CVS maintainer, BLFS Book
-creator, former LFS Book editor.
-
-James
-Iwanek <iwanek@linuxfromscratch.org> -- System Administration
-Team member.
-
-Nicholas
-Leippe <nicholas@linuxfromscratch.org> -- Wiki
+Nicholas Leippe
+<nicholas@linuxfromscratch.org> -- Wiki
maintainer.
-Anderson
-Lizardo <lizardo@linuxfromscratch.org> -- Website backend scripts
-creator and maintainer.
-
-Bill
-Maltby <bill@linuxfromscratch.org> -- LFS Project
-organizer.
-
-Alexander
-Patrakov <alexander@linuxfromscratch.org> -- LFS Book
-Editor (internationalization/localization).
+Anderson Lizardo
+<lizardo@linuxfromscratch.org> -- Website backend scripts
+maintainer.
Scot Mc
-Pherson <scot@linuxfromscratch.org> -- LFS NNTP gateway
-maintainer.
+Pherson <scot@linuxfromscratch.org> -- LFS Network News
+Transfer Protocol (NNTP) gateway maintainer.
Ryan
-Oliver <ryan@linuxfromscratch.org> -- Testing Team leader,
-Toolchain maintainer, co-creator of PLFS.
+Oliver <ryan@linuxfromscratch.org> -- Testing Team
+leader, Toolchain maintainer, co-creator of Pure LFS
+(PLFS).
James
-Robertson <jwrober@linuxfromscratch.org> -- Bugzilla maintainer,
-Wiki developer, LFS Book editor.
-
-Greg
-Schafer <greg@linuxfromscratch.org> -- Toolchain maintainer,
-Former LFS Book editor, co-creator of PLFS.
+Robertson <jwrober@linuxfromscratch.org> -- Bugzilla
+maintainer, Wiki developer, LFS Tecnical Writer.
Tushar
-Teredesai <tushar@linuxfromscratch.org> -- BLFS Book editor,
-Hints and Patches Projects maintainer.
+Teredesai <tushar@linuxfromscratch.org> -- BLFS Book
+editor, hints and patches projects maintainer.
Jeremy
-Utley <jeremy@linuxfromscratch.org> -- LFS Book editor, Bugzilla
-maintainer, LFS-Bootscripts Maintainer, LFS Server co-admin.
+Utley <jeremy@linuxfromscratch.org> -- LFS Technical
+Writer, Bugzilla maintainer, LFS Bootscripts Maintainer, LFS Server
+co-administrator.
-Zack
-Winkles <winkie@linuxfromscratch.org> -- LFS Book editor
-(Emerging Technologies), LFS-Bootscripts co-maintainer.
-
-Countless other people on the various LFS and BLFS
-mailing lists who are making this book happen by giving their suggestions,
-testing the book and submitting bug reports, instructions and their
+Countless other people on the various LFS and BLFS mailing lists
+who helped make this book possible by giving their suggestions,
+testing the book, and submitting bug reports, instructions, and their
experiences with installing various packages.
-
-Translators
+ Translators
@@ -118,177 +95,194 @@ Esparcia <macana@lfs-es.org> -- Spanish LFS translation
project.
Johan
-Lenglet <johan@linuxfromscratch.org> -- French LFS translation
-project.
-
-Anderson
-Lizardo <lizardo@linuxfromscratch.org> -- Portuguese LFS
+Lenglet <johan@linuxfromscratch.org> -- French LFS
translation project.
-Thomas Reitelbach
- <tr@erdfunkstelle.de> -- German LFS translation project.
-
+Anderson Lizardo
+<lizardo@linuxfromscratch.org> -- Portuguese LFS translation
+project.
+
+Thomas
+Reitelbach <tr@erdfunkstelle.de> -- German LFS
+translation project.
-
-Mirror Maintainers
+ Mirror Maintainers
-
-North American Mirrors
+ North American Mirrors
-Scott Kveton
-<scott@osuosl.org> -- lfs.oregonstate.edu mirror
+Scott
+Kveton <scott@osuosl.org> -- lfs.oregonstate.edu
+mirror
-Mikhail Pastukhov
-<miha@xuy.biz> -- lfs.130th.net mirror.
+Mikhail
+Pastukhov <miha@xuy.biz> -- lfs.130th.net
+mirror.
-Unknown User
-<unknown@unknown.org> -- lfs.crash404.com mirror.
+Unknown
+User <unknown@unknown.org> -- lfs.crash404.com
+mirror.
William Astle
-<lost@l-w.net> -- ca.linuxfromscratch.org mirror.
+<lost@l-w.net> -- ca.linuxfromscratch.org
+mirror.
-Jeremy Polen
-<jpolen@rackspace.com> -- us2.linuxfromscratch.org
+Jeremy
+Polen <jpolen@rackspace.com> -- us2.linuxfromscratch.org
mirror.
Tim Jackson
-<tim@idge.net> -- linuxfromscratch.idge.net mirror.
+<tim@idge.net> -- linuxfromscratch.idge.net
+mirror.
-Jeremy Utley
- <jeremy@linux-phreak.net> -- lfs.linux-phreak.net mirror.
-
+Jeremy
+Utley <jeremy@linux-phreak.net> -- lfs.linux-phreak.net
+mirror.
-
-South American Mirrors
+ South American Mirrors
-Manuel Canales
-Esparcia <manuel@linuxfromscratch.org> -- lfsmirror.lfs-es.org
-mirror.
+Manuel
+Canales Esparcia <manuel@linuxfromscratch.org> --
+lfsmirror.lfs-es.org mirror.
-Andres Meggiotto
-<sysop@mesi.com.ar> -- lfs.mesi.com.ar mirror.
+Andres
+Meggiotto <sysop@mesi.com.ar> -- lfs.mesi.com.ar
+mirror.
Eduardo B.
-Fonseca <ebf@aedsolucoes.com.br> -- br.linuxfromscratch.org
-mirror.
+Fonseca <ebf@aedsolucoes.com.br> --
+br.linuxfromscratch.org mirror.
-
-European Mirrors
+ European Mirrors
-Barna Koczka
-<barna@siker.hu> -- hu.linuxfromscratch.org mirror.
-
-UK Mirror Service
--- linuxfromscratch.mirror.ac.uk mirror.
-
-Martin Voss
-<Martin.Voss@ada.de> -- lfs.linux-matrix.net mirror.
-
-Unknown User
-<unknown@unknown.org> -- mirror.vtx.ch mirror
-
-Guido Passet
-<guido@primerelay.net> -- nl.linuxfromscratch.org
+Barna
+Koczka <barna@siker.hu> -- hu.linuxfromscratch.org
mirror.
-Bastiaan Jacques
-<baafie@planet.nl> -- lfs.pagefault.net mirror
-
-Roel
-Neefs <lfs-mirror@linuxfromscratch.rave.org> -- linuxfromscratch.rave.org mirror.
-
-Justin Knierim
-<justin@jrknierim.de> -- www.lfs-matrix.de mirror
-
-Stephan Brendel
-<stevie@stevie20.de> -- lfs.netservice-neuss.de
+UK Mirror
+Service -- linuxfromscratch.mirror.ac.uk
mirror.
-Unknown User
-<unknown@unknown.org> -- linuxfromscratch.je-zi.de
+Martin
+Voss <Martin.Voss@ada.de> -- lfs.linux-matrix.net
+mirror.
+
+Unknown
+User <unknown@unknown.org> -- mirror.vtx.ch
mirror
-Unknown User
-<unknown@unknown.org> -- linuxfromscratch.tuxcenter.net
+Guido
+Passet <guido@primerelay.net> -- nl.linuxfromscratch.org
+mirror.
+
+Bastiaan
+Jacques <baafie@planet.nl> -- lfs.pagefault.net
mirror
-Hagen Herrschaft
-<hrx@hrxnet.de> -- de.linuxfromscratch.org mirror.
+Roel Neefs
+<lfs-mirror@linuxfromscratch.rave.org> --
+linuxfromscratch.rave.org mirror.
-Antonin
-Sprinzl <Antonin.Sprinzl@tuwien.ac.at> -- at.linuxfromscratch.org
+Justin
+Knierim <justin@jrknierim.de> -- www.lfs-matrix.de
+mirror
+
+Stephan
+Brendel <stevie@stevie20.de> -- lfs.netservice-neuss.de
+mirror.
+
+Unknown
+User <unknown@unknown.org> -- linuxfromscratch.je-zi.de
+mirror
+
+Unknown
+User <unknown@unknown.org> --
+linuxfromscratch.tuxcenter.net mirror
+
+Hagen
+Herrschaft <hrx@hrxnet.de> -- de.linuxfromscratch.org
+mirror.
+
+Antonin Sprinzl
+<Antonin.Sprinzl@tuwien.ac.at> -- at.linuxfromscratch.org
mirror.
Fredrik
-Danerklint <fredan-lfs@fredan.org> -- se.linuxfromscratch.org
+Danerklint <fredan-lfs@fredan.org> --
+se.linuxfromscratch.org mirror.
+
+Parisian sysadmins
+<archive@doc.cs.univ-paris8.fr> -- www2.fr.linuxfromscratch.org
mirror.
-Parisian
-sysadmins <archive@doc.cs.univ-paris8.fr> --
-www2.fr.linuxfromscratch.org mirror.
+Alexander
+Velin <velin@zadnik.org> -- bg.linuxfromscratch.org
+mirror.
-Alexander Velin
-<velin@zadnik.org> -- bg.linuxfromscratch.org mirror.
-
-
-Dirk Webster <dirk@securewebservices.co.uk> --
+ Dirk
+Webster <dirk@securewebservices.co.uk> --
lfs.securewebservices.co.uk mirror
-Thomas Skyt
-<thomas@sofagang.dk> -- dk.linuxfromscratch.org mirror.
-
-Simon Nicoll
-<sime@dot-sime.com> -- uk.linuxfromscratch.org mirror.
-
-
-
-
-
-
-Asian Mirrors
-
-
-
-Pui Yong
-<pyng@spam.averse.net> -- sg.linuxfromscratch.org
+Thomas
+Skyt <thomas@sofagang.dk> -- dk.linuxfromscratch.org
mirror.
-Stuart Harris
-<stuart@althalus.me.uk> -- lfs.mirror.intermedia.com.sg
+Simon
+Nicoll <sime@dot-sime.com> -- uk.linuxfromscratch.org
+mirror.
+
+
+
+
+
+ Asian Mirrors
+
+
+
+Pui
+Yong <pyng@spam.averse.net> -- sg.linuxfromscratch.org
+mirror.
+
+Stuart
+Harris <stuart@althalus.me.uk> --
+lfs.mirror.intermedia.com.sg mirror
+
+Unknown
+User <unknown@unknown.org> -- lfs.mirror.if.itb.ac.id
mirror
-Unknown User
-<unknown@unknown.org> -- lfs.mirror.if.itb.ac.id mirror
-
-
-Australian Mirrors
+ Australian Mirrors
-Jason Andrade
-<jason@dstc.edu.au> -- au.linuxfromscratch.org mirror.
+Jason
+Andrade <jason@dstc.edu.au> -- au.linuxfromscratch.org
+mirror.
@@ -296,94 +290,33 @@ mirror
-
-Donators
+A very special thank you to our donators
-Dean Benson
-<dean@vipersoft.co.uk> for several monetary
+Dean
+Benson <dean@vipersoft.co.uk> for several monetary
contributions.
-DREAMWVR.COM for
-their past sponsorship of donating various resources to the LFS and related
-sub projects.
+Hagen
+Herrschaft <hrx@hrxnet.de> for donating a 2.2 GHz P4
+system, now running under the name of Lorien.
-Hagen Herrschaft
-<hrx@hrxnet.de> for donating a 2.2 GHz P4 system, now running under the
-name of lorien.
+VA
+Software who, on behalf of Linux.com, donated a VA Linux 420
+(former StartX SP2) workstation.
-O'Reilly for
-donating books on SQL and PHP.
+Mark Stone for donating Belgarath, the
+linuxfromscratch.org server.
-VA Software
-who, on behalf of Linux.com, donated
-a VA Linux 420 (former StartX SP2) workstation.
-
-Mark Stone for
-donating shadowfax, the first linuxfromscratch.org
-server, a 750 MHz P3 with 512 MB RAM and two 9 GB SCSI drives. When the server
-moved it was renamed to belgarath.
-
-Jesse
-Tie-Ten-Quee <highos@linuxfromscratch.org> for donating a Yamaha
-CDRW 8824E CD-writer.
-
-Countless other people on the various LFS mailing lists who are
-making this book better by giving their suggestions, submitting bug reports,
-and throwing in their criticism.
-
-
-
-
-
-
-Former Team Members and Contributors
-
-
-
-Timothy
-Bauscher <timothy@linuxfromscratch.org> -- LFS Book editor, Hints
-Project maintainer.
-
-Robert Briggs for originally donating the
-linuxfromscratch.org and
-linuxfromscratch.com domain names.
-
-Ian Chilton
-<ian@ichilton.co.uk> for maintaining the Hints project.
-
-Marc
-Heerdink <gimli@linuxfromscratch.org> -- LFS Book
-editor.
-
-Seth W.
-Klein <sklein@linuxfromscratch.org> -- LFS FAQ
-creator.
-
-Garrett
-LeSage <garrett@linuxart.com> -- Original LFS banner
-creator.
-
-Simon
-Perreault <nomis80@videotron.ca> -- Hints Project
-maintainer.
-
-Geert Poels
-<Geert.Poels@skynet.be> -- Original BLFS banner creator; based on the
-LFS banner by Garrett LeSage.
-
-Frank Skettino
-<bkenoah@oswd.org> for the initial design of the old website -- have a
-look at .
-
-Jesse
-Tie-Ten-Quee <highos@linuxfromscratch.org> for temporarily
-hosting the linuxfromscratch.org server, answering
-countless questions on IRC and having a great deal of patience.
+Countless other people on the various LFS mailing lists who made
+this book even better by giving their suggestions, submitting bug
+reports, and providing comments.
+
diff --git a/prologue/audience.xml b/prologue/audience.xml
index c769b9067..99f2d174e 100644
--- a/prologue/audience.xml
+++ b/prologue/audience.xml
@@ -7,90 +7,85 @@
Audience
-
-Who would want to read this book
+There are many reasons why somebody would want to read this
+book. The principle reason being to install a Linux system straight
+from the source code. A question many people raise is, why go
+through all the hassle of manually building a Linux system from
+scratch when you can just download and install an existing
+one?
That is a good question and is the impetus for this
+section of the book.
-There are many reasons why somebody would want to read this book. The
-principal reason being to install a Linux system straight from the source
-code. A question many people raise is Why go through all the hassle of
-manually building a Linux system from scratch when you can just download and
-install an existing one?
. That is a good question and is the impetus for
-this section of the book.
+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.
-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
-to you what makes Linux tick, 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.
+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, you 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.
-A key benefit of LFS is that you have more control of your system
-without relying on someone else's Linux implementation. With LFS, you are
-in the driver's seat and dictate every aspect of your system, such as the
-directory layout and bootscript setup. You also dictate where, why and how
-programs are installed.
-
-Another benefit of LFS is the ability to create a very compact Linux
-system. When installing a regular distribution, you are usually forced to
-install several programs which you are likely never to use. They're just
-sitting there wasting precious disk space (or worse, CPU cycles). It isn't
-difficult to build an LFS system of less than 100 MB. Does that still sound like a
-lot? A few of us have been working on creating a very small embedded LFS
-system. We successfully built a system that was just enough to run the Apache
-web server with approximately 8MB of disk space used. Further stripping could
-bring that down to 5 MB or less. Try that with a regular distribution.
+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. They
+waste precious disk space, or worse, CPU cycles. It isn't 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 just enough to run the Apache web server with
+approximately 8MB of disk space used. Further stripping could bring
+that 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.
We could compare Linux distributions to a hamburger you buy at a
-fast-food restaurant -- you have no idea what you are eating. LFS, on the
-other hand, doesn't give you a hamburger, but the recipe to make a hamburger.
-This allows you to review it, to omit unwanted ingredients, and to
-add your own ingredients which enhance the flavor of your burger. When you
-are satisfied with the recipe, you go on to preparing it. You make it just
-the way you like it: broil it, bake it, deep-fry it, barbecue it, or eat it
-tar-tar (raw).
+fast-food restaurant -- you have no idea what might be in what you are
+eating. LFS, on the other hand, doesn't give you a hamburger, but
+rather the recipe to make a hamburger. This allows you to review the
+recipe, omit unwanted ingredients, and add your own ingredients to
+enhance the flavor of your burger. When you are satisfied with the
+recipe, move on to preparing it. It can be made to exact
+specifications -- broil it, bake it, deep-fry it or barbecue
+it.
-Another analogy that we can use is that of comparing LFS with a
-finished house. LFS will give you the skeletal plan of a house, but it's up
-to you to build it. You have the freedom to adjust your plans as you
-go.
+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's 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.
-One last 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 you feel are needed. You don't
-have 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 actually fixes the
-problem (adequately).
+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, and 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.
-There are too many good reasons to build your own LFS system for them all
-to be listed here. This section is only the tip of the iceberg. As you
-continue in your LFS experience, you will find on your own the power that
+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 your computer boots,
+we recommend the From Power Up To Bash Prompt
HOWTO
+located at or on
+The Linux Documentation Project's (TLDP) website at .
+The HOWTO builds a bare 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.
+
+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.
-
-
-
-Who would not want to read this book
-
-There are probably some who, for whatever reason, would feel that they do not
-want to read this book. If you do not wish to build your own Linux system from
-scratch, then you probably don't want to read this book. Our goal is to help
-you build a complete and usable foundation-level system. If you only want to
-know what happens while your computer boots, then we recommend the From
-Power Up To Bash Prompt
HOWTO. The HOWTO builds a bare system which is
-similar to that of this book, but it focuses strictly on creating a system
-capable of booting to a BASH prompt.
-
-While you decide which to read, consider your objective. If you wish
-to build a Linux system while learning a bit along the way, then this book
-is probably your best choice. If your objective is strictly educational and
-you do not have any plans for your finished system, then the
-From Power Up To Bash Prompt
HOWTO is probably a better choice.
-
-The From Power Up To Bash Prompt
HOWTO is located at
- or on The Linux
-Documentation Project's website at
-.
-
-
-
+
diff --git a/prologue/dedication.xml b/prologue/dedication.xml
index 21494b098..8801f864f 100644
--- a/prologue/dedication.xml
+++ b/prologue/dedication.xml
@@ -5,6 +5,5 @@
]>
Dedication
-This book is dedicated to my loving and supportive wife
-Beverly Beekmans.
+This book is dedicated
diff --git a/prologue/foreword.xml b/prologue/foreword.xml
index 997f97f71..b96dd0713 100644
--- a/prologue/foreword.xml
+++ b/prologue/foreword.xml
@@ -7,21 +7,33 @@
Foreword
-Having used a number of different Linux distributions, I was never
-fully satisfied with any of them. I didn't like the arrangement of
-the bootscripts. I didn't like the way certain programs were configured by
-default. Much more of that sort of thing bothered me. Finally I realized
-that if I wanted full satisfaction from my Linux system I would have to
-build my own system from scratch, using only the source code. I resolved
-not to use pre-compiled packages of any kind, nor CD-ROM or boot disk that
-would install some basic utilities. I would use my current Linux system to
-develop my own.
+Six years ago I embarked on the adventure known as Linux. I did
+what most you guys have done: download a distribution, install it, and
+work with it for a while. Then you don't quite like it and you hear
+about a different distribution that is supposed to be great and fix
+everything your current distribution does wrong. So you try that new
+distribution out for a while. You may even repeat that same cycle a
+few times.
-This wild idea seemed very difficult at the time and often seemed
-an impossible task. After sorting out all kinds of problems, such as
-dependencies and compile-time errors, a custom-built Linux system was
-created that was fully operational. I called this system a Linux From Scratch
-system, or LFS for short.
+After you have tried out a number of different distributions,
+you find that each has its strengths and weaknesses, but you can't
+seem to find that one system that brings you the most satisfaction.
+Personally, I came to the conclusion that to be truly satisfied with
+my Linux system, I would have to somehow combine those different
+systems into one perfect
Linux system. It would then
+have all the strengths from various different systems, without their
+weaknesses. But that surely is an impossible and daunting task. Or is
+it?
+
+You can do better than simply combining several distributions
+into one. You can create your own Linux system from scratch.
+
+After figuring out things like circular dependencies, compile
+time errors and other related issues, a custom built Linux system was
+created and fully operational. I called this system a Linux From
+Scratch system, or LFS for short. This book will show you how it was
+done and how you can create your own LFS system, fully customized to
+your own needs and desires.
I hope you will have a great time working on your own LFS!
@@ -30,3 +42,4 @@ Gerard Beekmans
gerard@linuxfromscratch.org
+
diff --git a/prologue/organization.xml b/prologue/organization.xml
index c95a1907c..4b9748c8c 100644
--- a/prologue/organization.xml
+++ b/prologue/organization.xml
@@ -12,27 +12,30 @@
Part I - Introduction
-Part I explains a few important things on how to proceed with the
-installation, and gives meta-information about the book (version, changelog,
-acknowledgments, associated mailing lists, and so on).
+Part I explains a few important notes on how to proceed with the
+LFS installation. This section also provides meta-information about
+the book (version, changelog, acknowledgments, associated mailing
+lists, etc.).
Part II - Preparing for the build
-Part II describes how to prepare for the building process: making a
-partition, downloading the packages, and compiling temporary tools.
+Part II describes how to prepare for the building process?making
+a partition, downloading the packages, and compiling temporary
+tools.
Part III - Building the LFS system
-Part III guides you through the building of the LFS system: compiling and
-installing all the packages one by one, setting up the boot scripts, and
-installing the kernel. The resulting basic Linux system is the foundation upon
-which you can build other software, to extend your system in the way you like.
-At the end of the book you'll find a list of all of the programs, libraries and
-important files that have been installed as an easy to use reference.
+Part III guides the reader through the building of the LFS
+system -- 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
+extend 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.
diff --git a/prologue/prerequisites.xml b/prologue/prerequisites.xml
index 62ac031b9..bfe244f9e 100644
--- a/prologue/prerequisites.xml
+++ b/prologue/prerequisites.xml
@@ -7,34 +7,29 @@
Prerequisites
-This book assumes that its reader has a good deal of knowledge about
-using and installing Linux software. Before you begin building your LFS
-system, you should read the following HOWTOs:
+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:
-Software-Building-HOWTO
+Software-Building-HOWTO --
This is a comprehensive guide to building and installing
-generic
Unix software distributions under Linux. This HOWTO is
-available at .
-
+generic
Unix software distributions under Linux.
-The Linux Users' Guide
+The Linux Users' Guide --
-This guide covers the usage of assorted Linux software and is
-available at
-.
+This guide covers the usage of assorted Linux software.
-The Essential Pre-Reading Hint
+The Essential Pre-Reading Hint --
-This is an LFS Hint written specifically for new users of Linux. It is
-mostly a list of links to excellent sources of information on a wide range of
-topics. Any person attempting to install LFS, should at least have an
-understanding of many of the topics in this hint. It is available at
-
-
+This is an LFS Hint written specifically for users new to Linux. It
+also includes a list of links to excellent sources of information on a
+wide range of topics. Any person attempting to install LFS should have
+an understanding of many of the topics in this hint.
+
diff --git a/prologue/typography.xml b/prologue/typography.xml
index 86962c6ad..f780cf733 100644
--- a/prologue/typography.xml
+++ b/prologue/typography.xml
@@ -8,31 +8,34 @@
To make things easier to follow, there are a few typographical
-conventions used throughout the book. Following are some examples:
+conventions used throughout this book. This section contains some
+examples of the typographical format found throughout Linux From
+Scratch.
./configure --prefix=/usr
-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.
+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.
install-info: unknown option `--dir-file=/mnt/lfs/usr/info/dir'
-This form of text (fixed width text) is showing screen
-output, probably as the result of commands issued, and is also used to
-show filenames, such as /etc/ld.so.conf.
+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
+/etc/ld.so.conf.
Emphasis
-This form of text is used for several purposes in the
-book, mainly to emphasize important points or items.
+This form of text is used for several purposes in the book,
+mainly to emphasize important points or items.
-This form of text is used for hyperlinks, both within the
-book and to external pages such as HOWTOs, download locations and
-websites.
+This format is used for hyperlinks, both within the LFS
+community and to external pages, including HOWTOs, download locations,
+and websites.
cat > $LFS/etc/group << "EOF"
root:x:0:
@@ -40,15 +43,16 @@ bin:x:1:
......
EOF
-This type of section is used mainly when creating
-configuration files. The first command tells the system to create
-the file $LFS/etc/group from whatever is typed on the following lines until
-the sequence EOF is encountered. Therefore, this whole section is generally
-typed as seen.
+This type is used when creating configuration files. The first
+command tells the system to create the file
+$LFS/etc/group 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.
[REPLACED TEXT]
-This form of text is used to encapsulate text that is
-not to be typed as seen or copy and pasted.
+This format is used to encapsulate text that is not to be typed
+as seen or copy-and-pasted.
+