Changeset b157558 for chapter09

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

File:

• chapter09/theend.xml (modified) (1 diff)

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>