Changes in chapter07/cleanup.xml [b649e6b:9ee05b53]

File:

• chapter07/cleanup.xml (modified) (10 diffs)

chapter07/cleanup.xml

@@ -10 +10 @@
 
   <title>Cleaning up and Saving the Temporary System</title>
-  
+
   <sect2>
     <title>Cleaning</title>
@@ -21 +21 @@
     <para>Second, 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 non-autotools build systems.
+    shared libraries, especially when using non-autotools build systems.
     While still in chroot, remove those files now:</para>
 
@@ -27 +27 @@
 
     <para>
-      The current system size is now about 3 GB, however 
+      The current system size is now about 3 GB, however
       the /tools directory is no longer needed. It uses about
       1 GB of disk space.  Delete it now:
@@ -38 +38 @@
     <title>Backup</title>
 
+    <para>
+      At this point the essential programs and libraries have been created
+      and your current LFS system is in a good state. Your system can now be
+      backed up for later reuse. In case of fatal failures in the subsequent
+      chapters, it often turns out that removing everything and starting over
+      (more carefully) is the best option to recover. Unfortunately, all the
+      temporary files will be removed, too. To avoid spending extra time to
+      redo something which has been built successfully, creating a backup of
+      the current LFS system may prove useful.
+    </para>
+
     <note><para>
       All the remaining steps in this section are optional. Nevertheless,
@@ -43 +54 @@
       linkend="chapter-building-system"/>, the temporary files will be
       overwritten. So it may be a good idea to do a backup of the current
-      system as described below. 
+      system as described below.
     </para></note>
-  
+
     <para>
       The following steps are performed from outside the chroot
@@ -57 +68 @@
     </para>
 
+    <para>
+       If you have decided to make a backup, leave the chroot environment:
+    </para>
+
+<screen role="nodump"><userinput>exit</userinput></screen>
+
     <important>
-      <para>All of the following instructions are executed by
-        <systemitem class="username">root</systemitem>. Take extra
-        care about the commands you're going to run as mistakes
+      <para>
+        All of the following instructions are executed by
+        <systemitem class="username">root</systemitem> on your host system.
+        Take extra care about the commands you're going to run as mistakes
         here can modify your host system. Be aware that the
-        environment variable <envar>LFS</envar> 
-        is set for user <systemitem class="username">lfs</systemitem> by default 
-        but may <emphasis>not</emphasis> be set for 
-        <systemitem class="username">root</systemitem>. Whenever 
-        commands are to be executed by <systemitem class="username">root</systemitem>, 
+        environment variable <envar>LFS</envar>
+        is set for user <systemitem class="username">lfs</systemitem> by default
+        but may <emphasis>not</emphasis> be set for
+        <systemitem class="username">root</systemitem>.
+     </para>
+     <para>
+        Whenever commands are to be executed by <systemitem class="username">root</systemitem>,
         make sure you have set <envar>LFS</envar>.
+     </para>
+     <para>
         This has been discussed in <xref linkend='ch-partitioning-aboutlfs'/>.
       </para>
     </important>
 
-    <para>
-       Now, if you are making a backup, leave the chroot environment:
-    </para>
+    <para>Before making a backup, unmount the virtual file systems:</para>
 
-<screen role="nodump"><userinput>exit</userinput></screen>
+<screen role="nodump"><userinput>umount $LFS/dev/pts
+umount $LFS/{sys,proc,run,dev}</userinput></screen>
 
     <para>
-      At this point the essential programs and libraries have been created
-      and your current system is in a good state. Your system can now be
-      backed up for later reuse. In case of fatal failures in the subsequent
-      chapters, it often turns out that removing everything and starting over
-      (more carefully) is the best option to recover. Unfortunately, all the
-      temporary files will be removed, too. To avoid spending extra time to
-      redo something which has been built successfully, prepare a backup.
+      Make sure you have at least 1 GB free disk space (the source tarballs
+      will be included in the backup archive) on the filesystem containing
+      directory where you create the backup archive.
     </para>
 
     <para>
-      Make sure you have at least 1 GB free disk space (the source tarballs
-      will be included in the backup archive) in the home directory of user 
-      <systemitem class="username">root</systemitem>.
+      Note that the instructions below specify the home directory of the host
+      system's <systemitem class="username">root</systemitem> user, which is
+      typically found on the root filesystem.
     </para>
 
-    <para>Before we make a backup, unmount the virtual file systems:</para>
-
-<screen role="nodump"><userinput>umount $LFS/dev{/pts,}
-umount $LFS/{sys,proc,run}</userinput></screen>
+    <para>
+      Replace <envar>$HOME</envar> by a directory of your choice if you
+      do not want to have the backup stored in <systemitem
+      class="username">root</systemitem>'s home directory.
+    </para>
 
     <para>
@@ -108 +126 @@
           long time (over 10 minutes) even on a resonably fast system.
        </para>
-       
-       <para>
-          Also, ensure the <envar>LFS</envar> environment variable is set 
-          for the root user.
-       </para>
     </note>
 
-<screen role="nodump" revision="sysv"><userinput>cd $LFS 
+<screen role="nodump" revision="sysv"><userinput>cd $LFS
 tar -cJpf $HOME/lfs-temp-tools-&version;.tar.xz .</userinput></screen>
 
-<screen role="nodump" revision="systemd"><userinput>cd $LFS 
+<screen role="nodump" revision="systemd"><userinput>cd $LFS
 tar -cJpf $HOME/lfs-temp-tools-&versiond;.tar.xz .</userinput></screen>
 
-    <para>
-      Replace <envar>$HOME</envar> by a directory of your choice if you
-      do not want to have the backup stored in <systemitem 
-      class="username">root</systemitem>'s home directory.
-    </para>
   </sect2>
 
@@ -134 +142 @@
       In case some mistakes have been made and you need to start over, you can
       use this backup to restore the system and save some recovery time.
-      Since the sources are located under 
+      Since the sources are located under
       <filename class="directory">$LFS</filename>, they are included in the
       backup archive as well, so they do not need to be downloaded again. After
@@ -145 +153 @@
 
     <warning><para>The following commands are extremly dangerous.  If
-    you run <command>rm -rf ./*</command> as the root user and you 
-    do not change to the $LFS directory or the <envar>LFS</envar> 
-    environment variable is not set for the root user, it will destroy 
+    you run <command>rm -rf ./*</command> as the root user and you
+    do not change to the $LFS directory or the <envar>LFS</envar>
+    environment variable is not set for the root user, it will destroy
     your entire host system.  YOU ARE WARNED.</para></warning>
 
-<screen role="nodump" revision="sysv"><computeroutput>cd $LFS 
-rm -rf ./* 
+<screen role="nodump" revision="sysv"><computeroutput>cd $LFS
+rm -rf ./*
 tar -xpf $HOME/lfs-temp-tools-&version;.tar.xz</computeroutput></screen>
 
-<screen role="nodump" revision="systemd"><computeroutput>cd $LFS 
-rm -rf ./* 
+<screen role="nodump" revision="systemd"><computeroutput>cd $LFS
+rm -rf ./*
 tar -xpf $HOME/lfs-temp-tools-&versiond;.tar.xz</computeroutput></screen>
 
@@ -173 +181 @@
        </para>
     </important>
-    
+
   </sect2>