diff options
Diffstat (limited to 'chapter07/cleanup.xml')
| -rw-r--r-- | chapter07/cleanup.xml | 36 |
1 files changed, 16 insertions, 20 deletions
diff --git a/chapter07/cleanup.xml b/chapter07/cleanup.xml index 2a83e2d62..356f3c34e 100644 --- a/chapter07/cleanup.xml +++ b/chapter07/cleanup.xml @@ -13,15 +13,15 @@ <sect2> <title>Cleaning</title> - <para>First, remove the currently installed documentation to prevent them + <para>First, remove the currently installed documentation files to prevent them from ending up in the final system, and to save about 35 MB:</para> <screen><userinput>rm -rf /usr/share/{info,man,doc}/*</userinput></screen> <para>Second, on a modern Linux system, the libtool .la files are only - useful for libltdl. No libraries in LFS are expected to be loaded by - libltdl, and it's known that some .la files can cause BLFS packages - fail to build. Remove those files now:</para> + useful for libltdl. No libraries in LFS are loaded by + libltdl, and it's known that some .la files can cause BLFS package + failures. Remove those files now:</para> <screen><userinput>find /usr/{lib,libexec} -name \*.la -delete</userinput></screen> @@ -42,9 +42,9 @@ 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 + (more carefully) is the best way 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 + redo something which has been done successfully, creating a backup of the current LFS system may prove useful. </para> @@ -58,13 +58,12 @@ <para> The following steps are performed from outside the chroot - environment. That means, you have to leave the chroot environment + environment. That means you have to leave the chroot environment first before continuing. The reason for that is to get access to file system locations outside of the chroot - environment to store/read the backup archive which should + environment to store/read the backup archive, which ought not be placed within the - <filename class="directory">$LFS</filename> hierarchy for - safety reasons. + <filename class="directory">$LFS</filename> hierarchy. </para> <para> @@ -78,7 +77,7 @@ 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 + made 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 @@ -101,17 +100,14 @@ umount $LFS/{sys,proc,run,dev}</userinput></screen> <para> 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. + will be included in the backup archive) on the file system containing + the directory where you create the backup archive. </para> <para> 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> + typically found on the root file system. 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. @@ -149,7 +145,7 @@ tar -cJpf $HOME/lfs-temp-tools-&version;.tar.xz .</userinput></screen> 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 - checking that <envar>$LFS</envar> is set properly, + checking that <envar>$LFS</envar> is set properly, you can restore the backup by executing the following commands: </para> @@ -167,7 +163,7 @@ rm -rf ./* tar -xpf $HOME/lfs-temp-tools-&version;.tar.xz</computeroutput></screen> <para> - Again, double check that the environment has been setup properly + Again, double check that the environment has been set up properly and continue building the rest of the system. </para> @@ -175,7 +171,7 @@ tar -xpf $HOME/lfs-temp-tools-&version;.tar.xz</computeroutput></screen> <para> If you left the chroot environment to create a backup or restart building using a restore, remember to check that the virtual - filesystems are still mounted (<command>findmnt | grep + file systems are still mounted (<command>findmnt | grep $LFS</command>). If they are not mounted, remount them now as described in <xref linkend='ch-tools-kernfs'/> and re-enter the chroot environment (see <xref linkend='ch-tools-chroot'/>) before continuing. |