|
@@ -8,13 +8,16 @@
|
|
|
<sect1 id="ch-tools-stripping">
|
|
|
<?dbhtml filename="stripping.html"?>
|
|
|
|
|
|
- <title>Finishing Temporary Tools</title>
|
|
|
+ <title>Cleaning up and Saving the Temporary System</title>
|
|
|
|
|
|
- <para>
|
|
|
- The steps in this section are optional. Skip this section entirely
|
|
|
- if you are not really short on disk space and do not want to create
|
|
|
- a backup of the temporary tools.
|
|
|
- </para>
|
|
|
+ <note><para>
|
|
|
+ All the steps in this section are optional. Nevertheless, as soon
|
|
|
+ as you begin installing packages in <xref
|
|
|
+ linkend="chapter-building-system"/>, the temporary tools will be
|
|
|
+ overwritten. So it may be a good idea to do a backup of the temporary
|
|
|
+ tools as described below. The other steps are only needed if you are
|
|
|
+ really short on disk space.
|
|
|
+ </para></note>
|
|
|
|
|
|
<para>
|
|
|
The following steps are performed from outside the chroot
|
|
@@ -115,7 +118,7 @@ strip --strip-unneeded $LFS/tools/bin/*</userinput></screen>
|
|
|
built packages, your temporary tools are in a good state and might 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. Unfortunatly, all the
|
|
|
+ (more carefully) is the best option to recover. Unfortunately, all the
|
|
|
temporary tools will be removed, too. To avoid spending extra time to
|
|
|
redo something which has been built successfully, prepare a backup.
|
|
|
</para>
|
|
@@ -175,7 +178,7 @@ tar -xpf $HOME/lfs-temp-tools-&versiond;.tar.xz</computeroutput></screen>
|
|
|
<important>
|
|
|
<para>
|
|
|
If you left the chroot environment either to strip off debug
|
|
|
- symbols, create a backup or restart building using a restore,
|
|
|
+ symbols, create a backup, or restart building using a restore,
|
|
|
remember to mount the kernel virtual filesystems now again as
|
|
|
described in <xref linkend='ch-tools-kernfs'/> and re-enter
|
|
|
the chroot environment (see <xref linkend='ch-tools-chroot'/>)
|