From beb80e291d09a6ca6f1855b42ae3178514b0a848 Mon Sep 17 00:00:00 2001 From: Bruce Dubbs Date: Mon, 6 Sep 2021 09:32:47 -0500 Subject: [PATCH] Update text in Chapter 7 Backup/Restore sections Patch by Kevin Buckley. Also made minor clarification to umount commands. --- chapter01/changelog.xml | 10 +++++ chapter07/cleanup.xml | 90 ++++++++++++++++++++++------------------- 2 files changed, 59 insertions(+), 41 deletions(-) diff --git a/chapter01/changelog.xml b/chapter01/changelog.xml index 603b92eae..3e7a37aa8 100644 --- a/chapter01/changelog.xml +++ b/chapter01/changelog.xml @@ -43,6 +43,16 @@ appropriate for the entry or if needed the entire day's listitem. --> + + 2021-09-06 + + + [bdubbs] - Text clarifications in the backup/restore section + o fChapter 7. Thanks to Kevin Buckley for the patch. + + + + 2021-09-01 diff --git a/chapter07/cleanup.xml b/chapter07/cleanup.xml index 36af2cfaa..8e80bdc40 100644 --- a/chapter07/cleanup.xml +++ b/chapter07/cleanup.xml @@ -20,7 +20,7 @@ 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: find /usr/{lib,libexec} -name \*.la -delete @@ -37,6 +37,17 @@ Backup + + 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. + + All the remaining steps in this section are optional. Nevertheless, as soon as you begin installing packages in - - 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: + If you have decided to make 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 - temporary files will be removed, too. To avoid spending extra time to - redo something which has been built successfully, prepare a backup. - + + + All of the following instructions are executed by + root 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 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 . + + + + Before making a backup, unmount the virtual file systems: + +umount $LFS/dev/pts +umount $LFS/{sys,proc,run,dev} 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. + will be included in the backup archive) on the filesystem containing + directory where you create the backup archive. - Before we make a backup, unmount the virtual file systems: + + Note that the instructions below specify the home directory of the host + system's root user, which is + typically found on the root filesystem. + -umount $LFS/dev{/pts,} -umount $LFS/{sys,proc,run} + + Replace $HOME by a directory of your choice if you + do not want to have the backup stored in root's home directory. + Create the backup archive by running the following command: @@ -107,11 +125,6 @@ umount $LFS/{sys,proc,run} 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 @@ -120,11 +133,6 @@ 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. -