Ignore:
Timestamp:
08/08/2004 02:11:09 AM (20 years ago)
Author:
Gerard Beekmans <gerard@…>
Branches:
6.0
Children:
5ba3d1d
Parents:
6e41459
Message:

Completed global edits for upcoming 6.0 release

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

File:
1 edited

Legend:

Unmodified
Added
Removed

  • chapter06/strippingagain.xml

    r6e41459 ref13657  
    55<?dbhtml filename="strippingagain.html"?>
    66
    7 <para>If you are not a programmer and don't plan to do any debugging on your
    8 system software, you can shrink your system by about 200 MB by removing the
    9 debugging symbols from binaries and libraries. This causes no inconvenience
    10 other than not being able to debug the software fully any more.</para>
     7<para>If the intended user is not a programmer and does not plan to do
     8any debugging on the system software, the system size can be decreased
     9by about 200 MB by removing the debugging symbols from binaries and
     10libraries. This causes no inconvenience other than not being able to
     11debug the software fully anymore.</para>
    1112
    12 <para>Most people who use the command mentioned below don't experience any
    13 problems. But it is easy to make a typo and render your new system unusable, so
    14 before running the strip command it is probably a good idea to make a backup of
    15 the current situation.</para>
     13<para>Most people who use the command mentioned below do not
     14experience any difficulties. However, it is easy to make a typo and
     15render the new system unusable, so before running the strip command,
     16it is probably a good idea to make a backup of the current
     17situation.</para>
    1618
    17 <para>If you are going to perform the stripping, special care is needed to
    18 ensure you're not running any of the binaries that are about to be stripped.
    19 If you're not sure whether you entered chroot with the command given in
    20 <xref linkend="ch-system-chroot"/>, then first exit from chroot:</para>
     19<para>Before perform the stripping, take special care to ensure that
     20none of the binaries that are about to be stripped are running. If
     21unsure whether the user entered chroot with the command given in
     22<xref linkend="ch-system-chroot"/>, first exit from
     23chroot:</para>
    2124
    2225<screen><userinput>logout</userinput></screen>
    … …  
    2932    /tools/bin/bash --login</userinput></screen>
    3033
    31 <para>Now you can safely strip the binaries and libraries:</para>
     34<para>Now the binaries and libraries can be safely stripped:</para>
    3235
    3336<screen><userinput>/tools/bin/find /{,usr/}{bin,lib,sbin} -type f \
    3437   -exec /tools/bin/strip --strip-debug '{}' ';'</userinput></screen>
    3538
    36 <para>A large number of files will be reported as having their file format not
    37 recognized. These warnings can be safely ignored, they just mean that those
    38 files are scripts instead of binaries, no harm is done.</para>
     39<para>A large number of files will be reported as having their file
     40format not recognized. These warnings can be safely ignored. These
     41warnings indicate that those files are scripts instead of
     42binaries.</para>
    3943
    40 <para>If you are really tight on disk space, you may want to use
    41 <parameter>--strip-all</parameter> on the binaries in
    42 <filename class="directory">/{,usr/}{bin,sbin}</filename> to gain several more megabytes. But do
    43 <emphasis>not</emphasis> use this option on libraries: they would be
    44 destroyed.</para>
     44<para>If disk space is very tight, the
     45<parameter>--strip-all</parameter> options can be used on the binaries
     46in <filename class="directory">/{,usr/}{bin,sbin}</filename> to gain
     47several more megabytes. Do not use this option on libraries -- they will
     48be destroyed.</para>
    4549
    4650</sect1>
Note: See TracChangeset for help on using the changeset viewer.