Correcting the working dir, readding a lost paragraph, and alphabetizing.

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

appendixa/e2fsprogs-shortdesc.xml

@@ -6,13 +6,14 @@
  ext2 filesystem. It also supports the ext3 filesystem with journaling
  support.</para>
 
-<para><emphasis>Installed programs</emphasis>: badblocks, chattr, compile_et,
-debugfs, dumpe2fs, e2fsck, e2image, e2label, fsck, fsck.ext2, fsck.ext3,
-lsattr, mk_cmds, mke2fs, mkfs.ext2, mkfs.ext3, mklost+found, resize2fs,
-tune2fs, uuidgen, blkid, findfs and logsave.</para>
+<para><emphasis>Installed programs</emphasis>: badblocks, blkid, chattr,
+compile_et, debugfs, dumpe2fs, e2fsck, e2image, e2label, findfs, fsck,
+fsck.ext2, fsck.ext3, logsave, lsattr, mk_cmds, mke2fs, mkfs.ext2, mkfs.ext3,
+mklost+found, resize2fs, tune2fs and uuidgen.</para>
 
-<para><emphasis>Installed libraries</emphasis>: libcom_err.[a,so],
-libe2p.[a,so], libext2fs.[a,so], libss.[a,so], libuuid.[a,so] and libblkid.[a,so]</para>
+<para><emphasis>Installed libraries</emphasis>: libblkid.[a,so],
+libcom_err.[a,so], libe2p.[a,so], libext2fs.[a,so], libss.[a,so] and
+libuuid.[a,so]</para>
 
 </sect2>
 

chapter01/changelog.xml

@@ -96,6 +96,12 @@
 </itemizedlist>
 </listitem>
 
+<listitem><para>October 11h, 2003 [alex]: Adapted the required disk space
+values, as posted by Bruce Dubbs.</para></listitem>
+ 
+<listitem><para>October 11h, 2003 [alex]: Chapter 5 - Toolchain technical
+notes: Added and changed some markup.</para></listitem>
+ 
 <listitem><para>October 9th, 2003 [gerard]: Upgraded to
 lfs-bootscripts-1.12.</para></listitem>
 

chapter04/chapter04.xml

@@ -32,16 +32,16 @@ of the alternative means of downloading listed on
 <para>You'll need to store all the downloaded packages and patches somewhere
 that is conveniently available throughout the entire build. You'll also need a
 working directory in which to unpack the sources and build them. A scheme that
-works well is to use <filename>$LFS/usr/src/packages</filename> for all the
-downloaded files and <filename>$LFS/usr/src</filename> as the working
-directory. In this way, everything will be on the LFS partition and available
-during all stages of the building process.</para>
+works well is to use <filename>$LFS/tools/sources/packages</filename> for the
+tarballs, and <filename>$LFS/tools/sources</filename> as the working directory
+<emphasis>and</emphasis> as the place to store the patches. In this way,
+everything will be on the LFS partition and available during all stages of the
+building process.</para>
 
-<!--
-<para>So you may want to execute the following command:</para>
+<para>So you may want to execute the following command before starting
+your download session:</para>
 
-<screen><userinput>mkdir -p $LFS/usr/src/packages</userinput></screen>
--->
+<screen><userinput>mkdir -p $LFS/tools/sources/packages</userinput></screen>
 
 <!--
 <para>For your convenience the top of the list contains a link to a file

chapter05/binutils-pass2-inst.xml

@@ -29,6 +29,9 @@ variables that override the default optimization flags.</para>
 
 <screen><userinput>make </userinput></screen>
 
+<note><para>It's worth pointing out that running the Binutils test suite here
+is considered not as important running it in Chapter 6.</para></note>
+
 <para>Test the results (there should be no unexpected failures here, expected
 failures are fine):</para>