Changeset c071af0

Timestamp:

06/18/2020 07:14:06 AM (4 years ago)

Author:

Pierre Labastie <pieere@…>

Branches:

10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

80f8c02

Parents:

d66640e

Message:

Some finishing (?) touch in chapter
7

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@11953 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

Files:

• chapter07/chapter07.xml (modified) (1 diff)
• chapter07/stripping.xml (modified) (3 diffs)
• general.ent (modified) (1 diff)

chapter07/chapter07.xml

@@ -10 +10 @@
   <?dbhtml filename="chapter07.html"?>
 
-  <title>Entering Chroot and Building Additional Tools</title>
+  <title>Entering Chroot and Building Additional Temporary Tools</title>
 
   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="introduction.xml"/>

chapter07/stripping.xml

@@ -9 +9 @@
   <?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>
@@ -116 +119 @@
       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.
@@ -176 +179 @@
       <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

general.ent

@@ -1 @@
-<!ENTITY version         "SVN-20200617">
+<!ENTITY version         "SVN-20200618">
 <!ENTITY short-version   "svn">  <!-- Used below in &blfs-book; 
                                       Change to x.y for release but not -rc releases -->
 <!ENTITY generic-version "development"> <!-- Use "development"  or "x.y[-pre{x}]" -->
 
-<!ENTITY versiond        "20200617-systemd">
+<!ENTITY versiond        "20200618-systemd">
 <!ENTITY short-versiond  "systemd">
-<!ENTITY generic-versiond "20200615-systemd"> 
+<!ENTITY generic-versiond "systemd"> 
 
-<!ENTITY releasedate     "June 17th, 2020">
+<!ENTITY releasedate     "June 18th, 2020">
 
 <!ENTITY copyrightdate   "1999-2020"><!-- jhalfs needs a literal dash, not &ndash; -->