Changeset b157558

Timestamp:

02/22/2004 10:32:27 PM (20 years ago)

Author:

Alex Gronenwoud <alex@…>

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, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v5_1, v5_1_1, 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:

f89de33

Parents:

cd0c92d6

Message:

Moving the final strip from the last chapter to the end of chapter 6.

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

Files:

• chapter01/changelog.xml (modified) (3 diffs)
• chapter05/chapter05.xml (modified) (1 diff)
• chapter06/chapter06.xml (modified) (2 diffs)
• chapter08/kernel.xml (modified) (1 diff)
• chapter09/theend.xml (modified) (1 diff)

chapter01/changelog.xml

@@ -3 +3 @@
 <?dbhtml filename="changelog.html" dir="chapter01"?>
 
-<para>&version; - &releasedate;</para>
+<para>This is version &version; of the Linux From Scratch book, dated
+&releasedate;. If this book is more than two months old, a newer and better
+version is probably already available. To find out, please check one of the
+mirrors via <ulink url="&lfs-root;"/>.</para>
+ 
+<para>Below is a list of changes made since the previous release of the book,
+first a summary, then a detailed log.</para>
 
 <itemizedlist>
+
+<listitem><para>Upgraded to:</para>
+<itemizedlist>
+<listitem><para>less-382</para></listitem>
+<listitem><para>man-pages-1.66</para></listitem>
+<listitem><para>ncurses-5.4</para></listitem>
+</itemizedlist></listitem>
+
+<listitem><para>February 22nd, 2004 [alex]: Moved the stripping of the final
+system from chapter 9 to the end of chapter 6.</para></listitem>
 
 <listitem><para>February 22nd, 2004 [alex]: Chapter 6 - Coreutils and
@@ -14 +30 @@
 command.</para></listitem>
 
-<listitem><para>February 14th, 2004 [jeremy]: Chapter 6 - Upgraded Less
-to 382.</para></listitem>
+<listitem><para>February 14th, 2004 [jeremy]: Chapter 6 - Upgraded to
+Less-382.</para></listitem>
 
-<listitem><para>February 14th, 2004 [jeremy]: Chapters 5 & 6 - Upgraded
-ncurses to version 5.4, and removed references to etip patch.</para></listitem>
+<listitem><para>February 14th, 2004 [jeremy]: Chapters 5 + 6 - Upgraded to
+Ncurses-5.4, and removed references to the etip patch.</para></listitem>
 
 <listitem><para>February 12th, 2004 [jeremy]: Chapter 6 - Removed explicit
@@ -28 +44 @@
 
 <listitem><para>February 8th, 2004 [matt]: Chapter 6 - Updated to
-man-pages-1.66.</para></listitem>
+Man-pages-1.66.</para></listitem>
 
 <listitem><para>February 7th, 2004 [alex]: Chapter 1 - Moved the Conventions

chapter05/chapter05.xml

@@ -574 +574 @@
 <?dbhtml filename="stripping.html" dir="chapter05"?>
 
-<para>The steps in this section are optional. If your LFS partition is rather
-small, you will be glad to learn that you can throw away some unnecessary
-things. The executables and libraries you have built so far contain about 130 MB
-of unneeded debugging symbols. Remove those symbols like this:</para>
-
-<screen><userinput>strip --strip-unneeded /tools/{,s}bin/*
-strip --strip-debug /tools/lib/*</userinput></screen>
-
-<para>The first of the above commands will skip some twenty files, reporting
+<para>The steps in this section are optional, but if your LFS partition is
+rather small, you will be glad to learn that you can remove some unnecessary
+things. The executables and libraries you have built so far contain about 130
+MB of unneeded debugging symbols. Remove those symbols with:</para>
+
+<screen><userinput>strip --strip-debug /tools/lib/*
+strip --strip-unneeded /tools/{,s}bin/*</userinput></screen>
+
+<para>The last of the above commands will skip some twenty files, reporting
 that it doesn't recognize their file format. Most of them are scripts instead
 of binaries.</para>

chapter06/chapter06.xml

@@ -503 +503 @@
 
 
+<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 <command>gcc</command>'s <emphasis>-g</emphasis>
+option). This means that, 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>The inclusion of these debugging symbols, however, 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 somewhat, 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. For
+your convenience, the next section shows how to strip all debugging symbols
+from all programs and libraries. Information on other ways of optimizing your
+system can be found in the hint at <ulink
+url="&hints-root;optimization.txt"/>.</para>
+
+</sect1>
+
+
+<sect1 id="ch-system-strippingagain">
+<title>Stripping again</title>
+<?dbhtml filename="strippingagain.html" dir="chapter06"?>
+
+<para>If you are not a programmer and don't plan to do any debugging on your
+system software, you can shrink your system by about 200 MB by removing the
+debugging symbols from binaries and libraries. This causes no inconvenience
+other than not being able to debug the software fully any more.</para>
+
+<para>Most people who use the command mentioned below don't experience any
+problems. But it is easy to make a typo and render your new system unusable, so
+before running the strip command it is probably a good idea to make a backup of
+the current situation.</para>
+
+<para>If you are going to perform the stripping, special care is needed to
+ensure you're not running any of the binaries that are about to be stripped.
+If you're not sure whether you entered chroot with the command given in
+<xref linkend="ch-system-chroot"/>, then now exit from chroot and reenter it
+with the following commands:</para>
+
+<screen><userinput>logout; chroot $LFS /tools/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;/tools/bin/bash --login</userinput></screen>
+
+<para>Now you can safely strip the binaries and libraries:</para>
+
+<screen><userinput>/tools/bin/find /{,usr/}{bin,lib,sbin} -type f \
+&nbsp;&nbsp;&nbsp;-exec /tools/bin/strip --strip-debug '{}' ';'</userinput></screen>
+
+<para>A large number of files will be reported as having their file format not
+recognized. These warnings can be safely ignored, they just mean that those
+files are scripts instead of binaries, no harm is done.</para>
+
+<para>If you are really tight on disk space, you may want to use
+<emphasis>--strip-all</emphasis> on the binaries in
+<filename>/{,usr/}{bin,sbin}</filename> to gain several more megabytes. But do
+<emphasis>not</emphasis> use this option on libraries: they would be
+destroyed.</para>
+
+</sect1>
+
+
 <sect1 id="ch-system-revisedchroot">
 <title>Revised chroot command</title>
 <?dbhtml filename="revisedchroot.html" dir="chapter06"?>
 
-<para>From now on when you exit the chroot environment and wish to re-enter
+<para>From now on when you exit the chroot environment and wish to reenter
 it, you should run the following modified chroot command:</para>
 
@@ -522 +609 @@
 </sect1>
 
-
-&c6-aboutdebug;
-
 </chapter>
 

chapter08/kernel.xml

@@ -75 +75 @@
 <screen><userinput>make CC=/opt/gcc-2.95.3/bin/gcc modules_install</userinput></screen>
 
+<para>If you have a lot of modules and very little space, you may want to
+consider stripping and compressing the modules. For most people such compression
+isn't worth the trouble, but if you're really pressed for space, then have a look at
+<ulink url="http://www.linux-mips.org/archives/linux-mips/2002-04/msg00031.html"/>.</para>
+
 <para>As nothing is complete without documentation, build the manual pages
 that come with the kernel:</para>

chapter09/theend.xml

@@ -6 +6 @@
 been a long process, but we hope it was worth it. We wish you a lot of fun
 with your new shiny custom built Linux system.</para>
-
-<para>Now would be a good time to strip all debug symbols from 
-the binaries on your LFS system. If you are not a programmer and don't plan 
-on debugging your software, then you will be happy to know that you can 
-reclaim a few tens of megs by removing debug symbols. This process causes 
-no inconvenience other than not being able to debug the software fully 
-anymore, which is not an issue if you don't know how to debug.</para>
-
-<para>Disclaimer: 98% of the people who use the command mentioned below don't
-experience any problems. But do make a backup of your LFS system before
-you run this command. There's a slight chance it may backfire on you and
-render your system unusable (mostly by destroying your kernel modules
-and dynamic &amp; shared libraries). This is caused more often by typos
-than by a problem with the command used.</para>
-
-<para>Having said that, the --strip-debug option we use to strip is quite 
-harmless under normal circumstances. It doesn't strip anything vital from 
-the files. It also is quite safe to use --strip-all on regular programs
-(don't use that on libraries - they will be destroyed), but it's not as
-safe, and the space you gain is not all that much. But if you're tight on
-disk space every little bit helps, so decide for yourself. Please refer to
-the strip man page for other strip options you can use. The general idea
-is to not run strip on libraries (other than --strip-debug), just to be
-on the safe side.</para>
-
-<para>If you are planning to go ahead and perform the strip, special care is
-needed to ensure you're not running any binaries that are about to be stripped
--- including the active bash shell. Therefore you'll need to exit the chroot
-environment and reenter it using a modified chroot command:</para>
-
-<screen><userinput>logout
-chroot $LFS /tools/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;/tools/bin/bash --login</userinput></screen>
-
-<para>Now run the following command:</para>
-
-<screen><userinput>/tools/bin/find /{,usr/,usr/local/}{bin,sbin,lib} -type f \
-&nbsp;&nbsp;&nbsp;-exec /tools/bin/strip --strip-debug '{}' ';'</userinput></screen>
-
-<para>Quite a number of files will be reported as having their file format not
-recognized. Most of these are scripts instead of binaries. These warnings can
-be safely ignored.</para>
 
 <para>It may be a good idea to create an <filename>/etc/lfs-release</filename>