aboutsummaryrefslogtreecommitdiffstats
path: root/chapter06
diff options
context:
space:
mode:
authorAlex Gronenwoud <alex@linuxfromscratch.org>2004-02-23 22:09:27 +0000
committerAlex Gronenwoud <alex@linuxfromscratch.org>2004-02-23 22:09:27 +0000
commitf89de330228e5159bb2cda0c03b81f2b5b7e83aa (patch)
treeb3e93eac5579a0ae7d307939cd1487a925ecbbd3 /chapter06
parentb1575581743d136f81bb3c06aae38a6a556bef1f (diff)
Cleaning up the revision of chroot and reboot sections.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3259 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter06')
-rw-r--r--chapter06/aboutdebug.xml50
-rw-r--r--chapter06/chapter06.xml32
2 files changed, 25 insertions, 57 deletions
diff --git a/chapter06/aboutdebug.xml b/chapter06/aboutdebug.xml
deleted file mode 100644
index 6708deb54..000000000
--- a/chapter06/aboutdebug.xml
+++ /dev/null
@@ -1,50 +0,0 @@
-<sect1 id="ch-system-aboutdebug">
-<title>About debugging symbols</title>
-<?dbhtml filename="aboutdebug.html" dir="chapter06"?>
-
-<para>Most programs and libraries are, by default, compiled with debugging
-symbols included (with gcc option -g).</para>
-
-<para>When debugging a program or library that was compiled with debugging
-information included, the debugger can give you not only memory addresses
-but also the names of the routines and variables.</para>
-
-<para>But the inclusion of these debugging symbols enlarges a program or
-library significantly. To get an idea of the amount of space these symbols
-occupy, have a look at the following:</para>
-
-<itemizedlist>
-
-<listitem><para>a bash binary
-with debugging symbols: 1200 KB</para></listitem>
-
-<listitem><para>a bash binary
-without debugging symbols: 480 KB</para></listitem>
-
-<listitem><para>Glibc and GCC files (/lib and /usr/lib)
-with debugging symbols: 87 MB</para></listitem>
-
-<listitem><para>Glibc and GCC files
-without debugging symbols: 16 MB</para></listitem>
-
-</itemizedlist>
-
-<para>Sizes may vary a little, depending on which compiler was used and
-which C library. But when comparing programs with and without debugging
-symbols, the difference will generally be a factor between 2 and 5.</para>
-
-<para>As most people will probably never use a debugger on their system
-software, a lot of disk space can be regained by removing these symbols .</para>
-
-<para>To remove debugging symbols from a binary (which must be an a.out
-or ELF binary), run <command>strip --strip-debug filename</command>.
-Wildcards can be used to treat multiple files (use something like
-<userinput>strip --strip-debug $LFS/tools/bin/*</userinput>).</para>
-
-<para>For your convenience, <xref linkend="chapter-finalizing"/> includes one simple
-command to strip all debugging symbols from all programs and libraries on your
-system. Additional information on optimization can be found in the hint at
-<ulink url="&hints-root;optimization.txt"/>.</para>
-
-</sect1>
-
diff --git a/chapter06/chapter06.xml b/chapter06/chapter06.xml
index 287b94540..f3173733b 100644
--- a/chapter06/chapter06.xml
+++ b/chapter06/chapter06.xml
@@ -590,21 +590,39 @@ destroyed.</para>
<sect1 id="ch-system-revisedchroot">
-<title>Revised chroot command</title>
+<title>Cleaning up</title>
<?dbhtml filename="revisedchroot.html" dir="chapter06"?>
-<para>From now on when you exit the chroot environment and wish to reenter
-it, you should run the following modified chroot command:</para>
+<para>From now on, when you exit the chroot environment and wish to reenter
+it, you should use the following modified chroot command:</para>
<screen><userinput>chroot $LFS /usr/bin/env -i \
&nbsp;&nbsp;&nbsp;&nbsp;HOME=/root TERM=$TERM PS1='\u:\w\$ ' \
&nbsp;&nbsp;&nbsp;&nbsp;PATH=/bin:/usr/bin:/sbin:/usr/sbin \
&nbsp;&nbsp;&nbsp;&nbsp;/bin/bash --login</userinput></screen>
-<para>The reason being there is no longer any need to use programs from the
-<filename class="directory">/tools</filename> directory. However, we don't
-want to remove the <filename class="directory">/tools</filename> directory
-just yet. There is still some use for it towards the end of the book.</para>
+<para>The reason for this is that, since the programs in <filename
+class="directory">/tools</filename> are no longer needed, you may want to
+delete the whole directory and regain the space. Before actually deleting the
+directory, exit from chroot and reenter it with the above command. Also, before
+removing <filename class="directory">/tools</filename>, you may want to tar it
+up and store it in a safe place, in case you want build another LFS system
+soon.</para>
+
+<note><para>Removing <filename class="directory">/tools</filename> will also
+remove the temporary copies of Tcl, Expect and DejaGnu, which were used for
+running the toolchain tests. If you want to use these programs later on, you
+will need to recompile and re-install them. The installation instructions are
+the same as in <xref linkend="chapter-temporary-tools"/>, apart from changing
+the prefix from <emphasis>/tools</emphasis> to <emphasis>/usr</emphasis>. The
+BLFS book discusses a slightly different approach to installing Tcl, see <ulink
+url="&blfs-root;"/>.</para></note>
+
+<para>You may also want to move the packages and patches stored in <filename
+class="directory">/sources</filename> to a more usual location, such as
+<filename class="directory">/usr/src/packages</filename>, and remove the
+directory -- or simply delete the whole directory if you've burned its contents
+on a CD).</para>
</sect1>