From 9c753b58f1db4267ee47a990b118782773dedd96 Mon Sep 17 00:00:00 2001 From: David Bryant Date: Tue, 20 Dec 2022 13:57:22 -0600 Subject: Improve English idiom and make additional changes, for clarity. Rephrased a clumsy sentence. Broke a run-on sentence in two. Used adverbs, and the possessive case, where necessary. --- chapter08/stripping.xml | 44 ++++++++++++++++++++++---------------------- 1 file changed, 22 insertions(+), 22 deletions(-) (limited to 'chapter08') diff --git a/chapter08/stripping.xml b/chapter08/stripping.xml index d82b72ac1..eaabab5b7 100644 --- a/chapter08/stripping.xml +++ b/chapter08/stripping.xml @@ -12,39 +12,39 @@ 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. + 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. 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 strip commands, it is a good idea to make a backup of the LFS system in its current state. - A strip command with + A strip command with the --strip-unneeded 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). + dynamically linked binaries and shared libraries). - The debugging symbols for selected libraries are placed - in separate files. This debugging information is needed if running - regression tests that use The debugging symbols from selected libraries are preserved + in separate files. That debugging information is needed to run + regression tests with valgrind or gdb later in BLFS. + url='&blfs-book;/general/gdb.html'>gdb later, in BLFS. Note that strip 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 strip 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 strip 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 /tmp, strip them - there, and install them back with the install command. - Read the related entry in for the - rationale to use the install command here. + there, then reinstall them with the install command. + (The related entry in gives the + rationale for using the install command here.) 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 - 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. + 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. -- cgit v1.2.3-54-g00ecf