Changes in chapter07/cleanup.xml [615f5b8:9ee05b53]
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter07/cleanup.xml
r615f5b8 r9ee05b53 10 10 11 11 <title>Cleaning up and Saving the Temporary System</title> 12 12 13 13 <sect2> 14 14 <title>Cleaning</title> … … 21 21 <para>Second, the libtool .la files are only useful when linking with static 22 22 libraries. They are unneeded and potentially harmful when using dynamic 23 shared libraries, specially when using non-autotools build systems.23 shared libraries, especially when using non-autotools build systems. 24 24 While still in chroot, remove those files now:</para> 25 25 … … 27 27 28 28 <para> 29 The current system size is now about 3 GB, however 29 The current system size is now about 3 GB, however 30 30 the /tools directory is no longer needed. It uses about 31 31 1 GB of disk space. Delete it now: … … 38 38 <title>Backup</title> 39 39 40 <para> 41 At this point the essential programs and libraries have been created 42 and your current LFS system is in a good state. Your system can now be 43 backed up for later reuse. In case of fatal failures in the subsequent 44 chapters, it often turns out that removing everything and starting over 45 (more carefully) is the best option to recover. Unfortunately, all the 46 temporary files will be removed, too. To avoid spending extra time to 47 redo something which has been built successfully, creating a backup of 48 the current LFS system may prove useful. 49 </para> 50 40 51 <note><para> 41 52 All the remaining steps in this section are optional. Nevertheless, … … 43 54 linkend="chapter-building-system"/>, the temporary files will be 44 55 overwritten. So it may be a good idea to do a backup of the current 45 system as described below. 56 system as described below. 46 57 </para></note> 47 58 48 59 <para> 49 60 The following steps are performed from outside the chroot … … 57 68 </para> 58 69 70 <para> 71 If you have decided to make a backup, leave the chroot environment: 72 </para> 73 74 <screen role="nodump"><userinput>exit</userinput></screen> 75 59 76 <important> 60 <para>All of the following instructions are executed by 61 <systemitem class="username">root</systemitem>. Take extra 62 care about the commands you're going to run as mistakes 77 <para> 78 All of the following instructions are executed by 79 <systemitem class="username">root</systemitem> on your host system. 80 Take extra care about the commands you're going to run as mistakes 63 81 here can modify your host system. Be aware that the 64 environment variable <envar>LFS</envar> 65 is set for user <systemitem class="username">lfs</systemitem> by default 66 but may <emphasis>not</emphasis> be set for 67 <systemitem class="username">root</systemitem>. Whenever 68 commands are to be executed by <systemitem class="username">root</systemitem>, 82 environment variable <envar>LFS</envar> 83 is set for user <systemitem class="username">lfs</systemitem> by default 84 but may <emphasis>not</emphasis> be set for 85 <systemitem class="username">root</systemitem>. 86 </para> 87 <para> 88 Whenever commands are to be executed by <systemitem class="username">root</systemitem>, 69 89 make sure you have set <envar>LFS</envar>. 90 </para> 91 <para> 70 92 This has been discussed in <xref linkend='ch-partitioning-aboutlfs'/>. 71 93 </para> 72 94 </important> 73 95 74 <para> 75 Now, if you are making a backup, leave the chroot environment: 76 </para> 96 <para>Before making a backup, unmount the virtual file systems:</para> 77 97 78 <screen role="nodump"><userinput>exit</userinput></screen> 98 <screen role="nodump"><userinput>umount $LFS/dev/pts 99 umount $LFS/{sys,proc,run,dev}</userinput></screen> 79 100 80 101 <para> 81 At this point the essential programs and libraries have been created 82 and your current system is in a good state. Your system can now be 83 backed up for later reuse. In case of fatal failures in the subsequent 84 chapters, it often turns out that removing everything and starting over 85 (more carefully) is the best option to recover. Unfortunately, all the 86 temporary files will be removed, too. To avoid spending extra time to 87 redo something which has been built successfully, prepare a backup. 102 Make sure you have at least 1 GB free disk space (the source tarballs 103 will be included in the backup archive) on the filesystem containing 104 directory where you create the backup archive. 88 105 </para> 89 106 90 107 <para> 91 Make sure you have at least 1 GB free disk space (the source tarballs92 will be included in the backup archive) in the home directory of user93 <systemitem class="username">root</systemitem>.108 Note that the instructions below specify the home directory of the host 109 system's <systemitem class="username">root</systemitem> user, which is 110 typically found on the root filesystem. 94 111 </para> 95 112 96 <para>Before we make a backup, unmount the virtual file systems:</para> 97 98 <screen role="nodump"><userinput>umount $LFS/dev{/pts,} 99 umount $LFS/{sys,proc,run}</userinput></screen> 113 <para> 114 Replace <envar>$HOME</envar> by a directory of your choice if you 115 do not want to have the backup stored in <systemitem 116 class="username">root</systemitem>'s home directory. 117 </para> 100 118 101 119 <para> … … 108 126 long time (over 10 minutes) even on a resonably fast system. 109 127 </para> 110 111 <para>112 Also, ensure the <envar>LFS</envar> environment variable is set113 for the root user.114 </para>115 128 </note> 116 129 117 <screen role="nodump" ><userinput>cd $LFS130 <screen role="nodump" revision="sysv"><userinput>cd $LFS 118 131 tar -cJpf $HOME/lfs-temp-tools-&version;.tar.xz .</userinput></screen> 119 132 120 <para> 121 Replace <envar>$HOME</envar> by a directory of your choice if you 122 do not want to have the backup stored in <systemitem 123 class="username">root</systemitem>'s home directory. 124 </para> 133 <screen role="nodump" revision="systemd"><userinput>cd $LFS 134 tar -cJpf $HOME/lfs-temp-tools-&versiond;.tar.xz .</userinput></screen> 135 125 136 </sect2> 126 137 … … 131 142 In case some mistakes have been made and you need to start over, you can 132 143 use this backup to restore the system and save some recovery time. 133 Since the sources are located under 144 Since the sources are located under 134 145 <filename class="directory">$LFS</filename>, they are included in the 135 146 backup archive as well, so they do not need to be downloaded again. After … … 142 153 143 154 <warning><para>The following commands are extremly dangerous. If 144 you run <command>rm -rf ./*</command> as the root user and you 145 do not change to the $LFS directory or the <envar>LFS</envar> 146 environment variable is not set for the root user, it will destroy 155 you run <command>rm -rf ./*</command> as the root user and you 156 do not change to the $LFS directory or the <envar>LFS</envar> 157 environment variable is not set for the root user, it will destroy 147 158 your entire host system. YOU ARE WARNED.</para></warning> 148 159 149 <screen role="nodump" ><computeroutput>cd $LFS150 rm -rf ./* 160 <screen role="nodump" revision="sysv"><computeroutput>cd $LFS 161 rm -rf ./* 151 162 tar -xpf $HOME/lfs-temp-tools-&version;.tar.xz</computeroutput></screen> 163 164 <screen role="nodump" revision="systemd"><computeroutput>cd $LFS 165 rm -rf ./* 166 tar -xpf $HOME/lfs-temp-tools-&versiond;.tar.xz</computeroutput></screen> 152 167 153 168 <para> … … 166 181 </para> 167 182 </important> 168 183 169 184 </sect2> 170 185
Note:
See TracChangeset
for help on using the changeset viewer.