Author: pierre Date: Thu Jun 18 00:14:06 2020 New Revision: 11953 Log: Some finishing (?) touch in chapter 7
Modified: trunk/BOOK/chapter07/chapter07.xml trunk/BOOK/chapter07/stripping.xml trunk/BOOK/general.ent Modified: trunk/BOOK/chapter07/chapter07.xml ============================================================================== --- trunk/BOOK/chapter07/chapter07.xml Wed Jun 17 21:22:40 2020 (r11952) +++ trunk/BOOK/chapter07/chapter07.xml Thu Jun 18 00:14:06 2020 (r11953) @@ -9,7 +9,7 @@ <?dbhtml dir="chapter07"?> <?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"/> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"; href="changingowner.xml"/> Modified: trunk/BOOK/chapter07/stripping.xml ============================================================================== --- trunk/BOOK/chapter07/stripping.xml Wed Jun 17 21:22:40 2020 (r11952) +++ trunk/BOOK/chapter07/stripping.xml Thu Jun 18 00:14:06 2020 (r11953) @@ -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 @@ 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 @@ <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'/>) Modified: trunk/BOOK/general.ent ============================================================================== --- trunk/BOOK/general.ent Wed Jun 17 21:22:40 2020 (r11952) +++ trunk/BOOK/general.ent Thu Jun 18 00:14:06 2020 (r11953) @@ -1,13 +1,13 @@ -<!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 – --> -- http://lists.linuxfromscratch.org/listinfo/lfs-book FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
