From 02b26317cb151d15706308aa349ee3a1cde98f06 Mon Sep 17 00:00:00 2001 From: Bruce Dubbs Date: Thu, 12 Aug 2021 15:33:11 -0500 Subject: Rework cleaning up section of Chapter 7 Renamed chapter07/stripping.xml to chapter07/cleanup.xml Removed stripping from the end of Chapter 7. We suggest a 10 GB or larger partition in Section 2.4 - Creating a New Partition and the space used before cleaning up is only 3 GB. Stripping would free up about 300 MB more, but these files will soon be overwritten anyway. Remove /tools here to save about 1 GB. General reorginization and rewording. Chapter 8 stripping still needs to be updated after this change. --- chapter07/cleanup.xml | 178 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 178 insertions(+) create mode 100644 chapter07/cleanup.xml (limited to 'chapter07/cleanup.xml') diff --git a/chapter07/cleanup.xml b/chapter07/cleanup.xml new file mode 100644 index 000000000..69f3d2da1 --- /dev/null +++ b/chapter07/cleanup.xml @@ -0,0 +1,178 @@ + + + %general-entities; +]> + + + + + Cleaning up and Saving the Temporary System + + + Cleaning + + First, remove the currently installed documentation to prevent them + from ending up in the final system, and to save about 35 MB: + +rm -rf /usr/share/{info,man,doc}/* + + 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. + While still in chroot, remove those files now: + +find /usr/{lib,libexec} -name \*.la -delete + + + 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: + + +rm -rf /tools + + + + Backup + + + All the remaining steps in this section are optional. Nevertheless, + as soon as you begin installing packages in , the temporary files will be + overwritten. So it may be a good idea to do a backup of the current + system as described below. + + + + The following steps are performed from outside the chroot + 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 + not be placed within the + $LFS hierarchy for + safety reasons. + + + + All of the following instructions are executed by + root. 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 LFS + is set for user lfs by default + but may not be set for + root. Whenever + commands are to be executed by root, + make sure you have set LFS. + This has been discussed in . + + + + + Now, if you are making a backup, leave the chroot environment: + + +exit + + + 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 + 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) in the home directory of user + root. + + + Before we make a backup, unmount the virtual file systems: + +umount $LFS/dev{/pts,} +umount $LFS/{sys,proc,run} + + + Create the backup archive by running the following command: + + + + + Because the backup archive is compressed, it takes a relatively + long time (over 10 minutes) even on a resonably fast system. + + + + Also, ensure the LFS environment variable is set + for the root user. + + + +cd $LFS +tar -cJpf $HOME/lfs-temp-tools-&version;.tar.xz . + +cd $LFS +tar -cJpf $HOME/lfs-temp-tools-&versiond;.tar.xz . + + + Replace $HOME by a directory of your choice if you + do not want to have the backup stored in root's home directory. + + + + + Restore + + + 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 + $LFS, they are included in the + backup archive as well, so they do not need to be downloaded again. After + checking that $LFS is set properly, + restore the backup by executing the following commands: + + + + + The following commands are extremly dangerous. If + you run rm -rf ./* as the root user and you + do not change to the $LFS directory or the LFS + environment variable is not set for the root user, it will destroy + your entire host system. YOU ARE WARNED. + +cd $LFS +rm -rf ./* +tar -xpf $HOME/lfs-temp-tools-&version;.tar.xz + +cd $LFS +rm -rf ./* +tar -xpf $HOME/lfs-temp-tools-&versiond;.tar.xz + + + Again, double check that the environment has been setup properly + and continue building the rest of the system. + + + + + 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 (findmnt | grep + $LFS). If they are not mounted, remount them now as + described in and re-enter the chroot + environment (see ) before continuing. + + + + + + -- cgit v1.2.3-54-g00ecf