Updates to the rest of cross2 Chapter 7.

git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/cross2@11919 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

1 files changed, 22 insertions, 27 deletions

diff --git a/chapter07/stripping.xml b/chapter07/stripping.xml
index efb1af3c5..66b20d4fc 100644
--- a/chapter07/stripping.xml
+++ b/chapter07/stripping.xml
@@ -28,37 +28,33 @@
 strip --strip-unneeded /usr/{,s}bin/*
 strip --strip-unneeded /tools/bin/*</userinput></screen>
 
-    <para>These commands will skip a number of files, reporting that it does not
+    <para>These commands will skip a number of files reporting that it does not
     recognize their file format. Most of these are scripts instead of binaries.
-    Note that we use the <command>strip</command> program built in
+    <!--Note that we use the <command>strip</command> program built in
     <quote>Binutils pass 1</quote>, since it is the one that knows how to strip
-    our cross-compiled programs.</para>
-  <!-- Normally, the host "strip" could be used too, since it is actually the
-  same computer. But Some old versions of binutils may generate buggy crt1.o
-  and the like, because they do not know about recently introduced symbol
-  types. For more details,
-  see https://sourceware.org/bugzilla/show_bug.cgi?id=22875-->
-
-    <para>Take care <emphasis>not</emphasis> to use
+    our cross-compiled programs.--></para>
+
+    <para>Take care <emphasis>NOT</emphasis> to use
     <parameter>--strip-unneeded</parameter> on the libraries. The static
     ones would be destroyed and the toolchain packages would need to be
     built all over again.</para>
 
-    <para>To save more, remove the documentation:</para>
+    <para>To save more space, remove the documentation:</para>
 
 <screen><userinput>rm -rf /usr/{,share}/{info,man,doc}</userinput></screen>
 
     <para>The libtool .la files are only useful when linking with static
     libraries. They are unneeded, and potentially harmful, when using dynamic
-    shared libraries, specially when using also non-autotools build systems.
+    shared libraries, specially when using non-autotools build systems.
     Remove those files now:</para>
 
 <screen><userinput>find /usr/{lib,libexec} -name \*.la -delete</userinput></screen>
 
-    <para>At this point, you should have at least 3 GB of free space in
-    <envar>$LFS</envar> that can be used to build and install Glibc and Gcc in
+    <para>At this point, you should have at least 5 GB of free space on the
+    chroot partition that can be used to build and install Glibc and Gcc in
     the next phase. If you can build and install Glibc, you can build and install
-    the rest too.</para>
+    the rest too. You can check the free disk space with the command 
+    <command>df -h /</command>.</para>
 
   </sect2>
 
@@ -70,9 +66,9 @@ strip --strip-unneeded /tools/bin/*</userinput></screen>
       a backup. When every check has passed successfully in the previously 
       built packages, your temporary tools are in a good state and might be
       backed up for later reuse. In case of fatal failures in the subsequent
-      sections, it often turns out that removing everything and starting over
+      chapters, it often turns out that removing everything and starting over
       (more carefully) is the best option to recover. Unfortunatly, all the
-      temporary tools will be removed, too. To avoid extra time to redo
+      temporary tools will be removed, too. To avoid the extra time needed to redo
       something which has been built successfully, prepare a backup.
     </para>
 
@@ -83,14 +79,13 @@ strip --strip-unneeded /tools/bin/*</userinput></screen>
       <systemitem class="username">lfs</systemitem>. Leaving the 
       chroot environment is required as the backup should be stored
       outside of the <filename class="directory">$LFS</filename> directory
-      but those cannot be accessed when in chroot. Leave chroot environment
+      but those cannot be accessed when in chroot. Leave the chroot environment
       and unmount the virtual kernel filesystems:
     </para>
 
 <screen role="nodump"><userinput>exit
 umount $LFS/dev{/pts,}
-umount $LFS/{sys,proc,run}
-</userinput></screen>
+umount $LFS/{sys,proc,run}</userinput></screen>
 
     <para>Create the backup archive:</para>
 <screen role="nodump"><userinput>cd $LFS &amp;&amp;
@@ -98,12 +93,12 @@ tar -cJpf $HOME/temp-tools.tar.xz .
 </userinput></screen>
 
     <para>
-      In case you have to start over as some mistakes has been made, you can
-      use this backup to restore the temporary tools and save some time on
-      the way to recover. Since the sources are located under 
+      In case some mistakes have been made and you need to start over, you can
+      use this backup to restore the temporary tools and save some irecovery time.
+      Since the sources are located under 
       <filename class="directory">$LFS</filename>, they are included in the
       backup archive as well, so you need not to download them again. After
-      checking that <filename class="directory">$LFS</filename> is set proper,
+      checking that <filename class="directory">$LFS</filename> is set properly,
       restore the backup by executing the following commands:
     </para>
 
@@ -113,8 +108,8 @@ tar -xpf $HOME/temp-tools.tar.xz
 </userinput></screen>
 
     <para>
-      Again, double check that the environment has been setup proper and
-      continue building the rest of the system.
+      Again, double check that the environment has been setup properly
+      and continue building the rest of the system.
     </para>
 
     <important>
@@ -122,7 +117,7 @@ tar -xpf $HOME/temp-tools.tar.xz
       If you left the chroot environment either to create a backup
       or restart building using a restore, remember to mount the
       kernel virtual filesystems as described in <xref
-      linkend='ch-tools-kernfs'/> and enter the
+      linkend='ch-tools-kernfs'/> and re-enter the
       chroot environment (see <xref
       linkend='ch-tools-chroot'/>) again before continuing.</para>
     </important>