gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-07-16 17:25:08 +01:00
Code Issues Packages Projects Releases Wiki Activity

Improve English idiom and make additional changes, for clarity.

Browse Source 
Rephrased a clumsy sentence. Broke a run-on sentence in two.
Used adverbs, and the possessive case, where necessary.
This commit is contained in:
David Bryant 2022-12-20 13:57:22 -06:00
parent 0785a5e6dd
commit 9c753b58f1
1 changed files with 22 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

44
chapter08/stripping.xml
View File

@ -12,39 +12,39 @@
<para>This section is optional. If the intended user is not a
programmer and does not plan to do
any debugging on the system software, the system size can be decreased
by about 2 GB by removing the debugging symbols and unneeded symbol table
entries from binaries and libraries. This causes no inconvenience other
than not being able to debug the software fully anymore.</para>
any debugging of the system software, the system's size can be decreased
by some 2 GB by removing the debugging symbols, and some unnecessary symbol table
entries, from binaries and libraries. This causes no real inconvenience for
a typical Linux user.</para>
<para>Most people who use the commands mentioned below do not
experience any difficulties. However, it is easy to make a typo and
render the new system unusable, so before running the
experience any difficulties. However, it is easy to make a mistake and
render the new system unusable. So before running the
<command>strip</command> commands, it is a good idea to make a
backup of the LFS system in its current state.</para>
<para>A <command>strip</command> command with
<para>A <command>strip</command> command with the
<parameter>--strip-unneeded</parameter> option removes all debug symbols
from a binary or library. And, it removes all symbol table entries not
from a binary or library. It also removes all symbol table entries not
needed by the linker (for static libraries) or dynamic linker (for
dynamic-linked binaries and shared libraries).</para>
dynamically linked binaries and shared libraries).</para>
<para>The debugging symbols for selected libraries are placed
in separate files. This debugging information is needed if running
regression tests that use <ulink
<para>The debugging symbols from selected libraries are preserved
in separate files. That debugging information is needed to run
regression tests with <ulink
url='&blfs-book;/general/valgrind.html'>valgrind</ulink> or <ulink
url='&blfs-book;/general/gdb.html'>gdb</ulink> later in BLFS.
url='&blfs-book;/general/gdb.html'>gdb</ulink> later, in BLFS.
</para>
<para>Note that <command>strip</command> will overwrite the binary or library
file it is processing. This can crash the processes using code or data from
the file. If the process running <command>strip</command> itself is
affected, the binary or library being stripped can be destroyed and can
make the system completely unusable. To avoid it, we'll copy some libraries
the file. If the process running <command>strip</command> is
affected, the binary or library being stripped can be destroyed; this can
make the system completely unusable. To avoid this problem we copy some libraries
and binaries into <filename class="directory">/tmp</filename>, strip them
there, and install them back with the <command>install</command> command.
Read the related entry in <xref linkend="pkgmgmt-upgrade-issues"/> for the
rationale to use the <command>install</command> command here.</para>
there, then reinstall them with the <command>install</command> command.
(The related entry in <xref linkend="pkgmgmt-upgrade-issues"/> gives the
rationale for using the <command>install</command> command here.)</para>
<note><para>The ELF loader's name is ld-linux-x86-64.so.2 on 64-bit systems
and ld-linux.so.2 on 32-bit systems. The construct below selects the
@ -111,8 +111,8 @@ done
unset BIN LIB save_usrlib online_usrbin online_usrlib
</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
indicate that those files are scripts instead of binaries.</para>
<para>A large number of files will be flagged as errors because their file
format is not recognized. These warnings can be safely ignored. They
indicate that those files are scripts, not binaries.</para>
</sect1>