Text updates from Matt

git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/multi-arch/BOOK@4993 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

6 files changed, 50 insertions, 47 deletions

diff --git a/chapter01/changelog.xml b/chapter01/changelog.xml
index e967eb120..d18ded5bf 100644
--- a/chapter01/changelog.xml
+++ b/chapter01/changelog.xml
@@ -84,7 +84,7 @@ first a summary, then a detailed log.</para>
 <listitem><para>Changelog Entries:</para>
 
 <itemizedlist>
-<listitem><para>April 12, 2005 [manuel]</para>
+<listitem><para>April 17, 2005 [manuel]</para>
 <itemizedlist>
 <listitem><para>Updated: Arch: All - Updated the stylesheets to use
 DocBook-XSL 1.68.1.</para></listitem>
@@ -93,6 +93,15 @@ DocBook-XSL 1.68.1.</para></listitem>
 </itemizedlist>
 
 <itemizedlist>
+<listitem><para>April 16, 2005 [matt]</para>
+<itemizedlist>
+<listitem><para>Updated: Arch: All - Updated documentation. Contributed by
+Ken Moffat, Alexander Patrakov, Andrew Benton, Allard Welter, and Peter Ennis</para></listitem>
+</itemizedlist>
+</listitem>
+</itemizedlist>
+
+<itemizedlist>
 <listitem><para>April 15, 2005 [jim]</para>
 <itemizedlist>
 <listitem><para>Updated: Arch: All - Udev to 057.</para></listitem>
diff --git a/chapter01/how.xml b/chapter01/how.xml
index b2390fb48..2654ce7d3 100644
--- a/chapter01/how.xml
+++ b/chapter01/how.xml
@@ -37,22 +37,18 @@ to compile a compiler, you need a compiler.</para>
 <para><xref linkend="chapter-temporary-tools"/> also shows the user how
 to build a first pass of the toolchain, including Binutils and GCC
 (first pass basically means these two core packages will be
-re-installed a second time). The programs from these packages will be
-linked statically in order to be used independently of the host
-system. The next step is to build Glibc, the C library. Glibc will be
-compiled by the toolchain programs built in the first pass. Then, a
-second pass of the toolchain will be built. This time, the toolchain
-will be dynamically linked against the newly built Glibc. The
-remaining <xref linkend="chapter-temporary-tools"/> packages are built
-using this second pass toolchain. When this is done, the LFS
-installation process will no longer depend on the host distribution,
-with the exception of the running kernel.</para>
+re-installed a second time). The next step is to build Glibc, the C library.
+Glibc will be compiled by the toolchain programs built in the first pass. Then,
+a second pass of the toolchain will be built. This time, the toolchain will be
+dynamically linked against the newly built Glibc. The remaining
+<xref linkend="chapter-temporary-tools"/> packages are built using this second
+pass toolchain. When this is done, the LFS installation process will no longer
+depend on the host distribution, with the exception of the running kernel.
+</para>
 
 <para>While this may initially seem like a lot of work to get away
 from a host distribution, a full technical explanation is provided at
-the beginning of <xref linkend="chapter-temporary-tools"/>, 
-including notes on the differences between
-statically and dynamically-linked programs.</para>
+the beginning of <xref linkend="chapter-temporary-tools"/>.</para>
 
 <para>In <xref linkend="chapter-building-system"/>, the full LFS system is
 built. The chroot (change root) program is used to enter a virtual
diff --git a/chapter06/hotplug.xml b/chapter06/hotplug.xml
index 4b5efbb01..3931f56bc 100644
--- a/chapter06/hotplug.xml
+++ b/chapter06/hotplug.xml
@@ -47,10 +47,6 @@ that reason, remove the network hotplug agent:</para>
 
 <screen><userinput>rm -f /etc/hotplug/net.agent</userinput></screen>
 
-<para>Create a file that is necessary for the logging of hotplug events:</para>
-
-<screen><userinput>touch /var/log/hotplug/events</userinput></screen>
-
 <para>Create a directory for storing firmware that can be loaded by 
 <command>hotplug</command>:</para>
 
diff --git a/chapter07/profile.xml b/chapter07/profile.xml
index 9aed251cb..7827b141f 100644
--- a/chapter07/profile.xml
+++ b/chapter07/profile.xml
@@ -61,27 +61,40 @@ environment variable that makes <application>Bash</application> and
 <para>Replace <replaceable>[ll]</replaceable> below with the
 two-letter code for the desired language (e.g., <quote>en</quote>) and
 <replaceable>[CC]</replaceable> with the two-letter code for the
-appropriate country (e.g., <quote>GB</quote>). It may also be
-necessary to specify (and this is actually the preferred form) the
-character encoding (e.g.  <quote>iso8859-1</quote>) after a dot (so
-that the result is <quote>en_GB.iso8859-1</quote>).  Issue the
-following command for more information:</para>
-
-<screen><userinput>man 3 setlocale</userinput></screen>
+appropriate country (e.g., <quote>GB</quote>).
+<replaceable>[charmap]</replaceable> should be replaced with the
+canonical charmap for your chosen locale.</para>
 
 <para>The list of all locales supported by Glibc can be obtained by running
 the following command:</para>
 
 <screen><userinput>locale -a</userinput></screen>
 
+<para>Locales can have a number of synonyms, e.g. <quote>ISO-8859-1</quote> is
+also referred to as <quote>iso8859-1</quote> and <quote>iso88591</quote>.
+Some applications cannot handle the various synonyms correctly, so it is safest
+to choose the canonical name for a particular locale.  To determine the
+canonical name, run the following command, where
+<replaceable>[locale name]</replaceable> is the output given by
+<command>locale -a</command> for your preferred locale
+(<quote>en_GB.iso88591</quote> in our example).</para>
+
+<screen><userinput>LC_ALL=<replaceable>[locale name]</replaceable> locale charmap</userinput></screen>
+
+<para>For the <quote>en_GB.iso88591</quote> locale, the above command
+will print:</para>
+
+<screen>ISO-8859-1</screen>
+
+<para>This results in in a final locale setting of <quote>en_GB.ISO-8859-1</quote>.</para>
+
 <para>Once the proper locale settings have been determined, create the
 <filename>/etc/profile</filename> file:</para>
 
 <screen><userinput>cat &gt; /etc/profile &lt;&lt; "EOF"
 <literal># Begin /etc/profile
 
-export LC_ALL=<replaceable>[ll]</replaceable>_<replaceable>[CC]</replaceable>
-export LANG=<replaceable>[ll]</replaceable>_<replaceable>[CC]</replaceable>
+export LANG=<replaceable>[ll]</replaceable>_<replaceable>[CC]</replaceable>.<replaceable>[charmap]</replaceable>
 export INPUTRC=/etc/inputrc
 
 # End /etc/profile</literal>
diff --git a/chapter07/udev.xml b/chapter07/udev.xml
index c948fda9d..c8db14c71 100644
--- a/chapter07/udev.xml
+++ b/chapter07/udev.xml
@@ -30,7 +30,7 @@ created each time the system boots, they will be stored on a
 <systemitem class="filesystem">ramfs</systemitem> (a file system that
 resides entirely in memory and does not take up any disk space).
 Device nodes do not require much disk space, so the memory that is
-used in negligable.</para>
+used is negligible.</para>
 
 <sect2>
 <title>History</title>
@@ -152,29 +152,18 @@ immediately accessible.</para>
 <sect2>
 <title>Handling Hotpluggable/Dynamic Devices</title>
 
-<para>When you plug in a device, such a Universal Serial Bus (USB) MP3 player, the kernel
+<para>When you plug in a device, such as a Universal Serial Bus (USB) MP3 player, the kernel
 recognizes that the device is now connected and generates a hotplug
 event. If the driver is already loaded (either because it was compiled
 into the kernel or because it was loaded via the
 <command>S05modules</command> bootscript), <command>udev</command> will
 be called upon to create the relevant device node(s) according to the
 <systemitem class="filesystem">sysfs</systemitem> data available in
-<filename class="directory">/sys</filename>.  If the driver for the
-just plugged in device is available as a module but currently unloaded,
-then attaching the device to the system will only cause the kernel's
-bus driver to generate a hotplug event that notifies userspace of the
-new device connection and it not being attached to a driver. In
-effect, nothing happens and the device itself is not usable
-yet.</para>
-
-<para>If building a system that has a lot of drivers compiled as
-modules rather than directly built into the kernel, using the
-<command>S05modules</command> may not be practical. The Hotplug
-package (see <ulink url="http://linux-hotplug.sourceforge.net/"/>) can
-be beneficial in these cases. When the Hotplug package is installed,
-it will respond to the aforementioned kernel's bus driver hotplug
-events. The Hotplug package will load the appropriate module and make
-this device available by creating the device node(s) for it.</para>
+<filename class="directory">/sys</filename>.</para>
+
+<para>If the driver for the just plugged in device is available as a module but
+currently unloaded, the Hotplug package will load the appropriate module
+and make this device available by creating the device node(s) for it.</para>
 </sect2>
 
 <sect2>
diff --git a/prologue/foreword.xml b/prologue/foreword.xml
index 7f2c31288..a7f584da9 100644
--- a/prologue/foreword.xml
+++ b/prologue/foreword.xml
@@ -7,7 +7,7 @@
 <title>Foreword</title>
 <?dbhtml filename="foreword.html"?>
 
-<para>My adventures in Linux began six years ago when I downloaded and
+<para>My adventures in Linux began in 1998 when I downloaded and
 installed my first distribution. After working with it for awhile, I
 discovered issues I definitely would have liked to see improved upon.
 For example, I didn't like the arrangement of the bootscripts or the way
@@ -37,7 +37,7 @@ short.</para>
 <para>As I shared my goals and experiences with other members of the
 Linux community, it became apparent that there was sustained interest
 in the ideas set forth in my Linux adventures. Such custom-built LFS
-systems not only to meet user specifications and requirements, but
+systems serve not only to meet user specifications and requirements, but
 also serve as an ideal learning opportunity for programmers and system
 administrators to enhance their Linux skills. Out of this broadened
 interest, the Linux From Scratch Project was born.</para>