Changeset f6bcc50 for final-system/common

Timestamp:

Feb 21, 2006, 1:29:15 AM (19 years ago)

Author:

Jim Gifford <clfs@…>

Children:

a9c7b83

Parents:

844eb89

Message:

r803@server (orig r801): jim | 2005-12-02 08:36:39 -0800

r880@server: jim | 2005-12-02 08:36:09 -0800
Text Updates from G. Moko

Location:

final-system/common

Files:

• aboutdebug.xml (modified) (2 diffs)
• shadow.xml (modified) (1 diff)
• stripping.xml (modified) (4 diffs)

final-system/common/aboutdebug.xml

@@ -11 +11 @@
   <title>About Debugging Symbols</title>
 
-  <para>Most programs and libraries are, by default, compiled with debugging
+  <para os="a">Most programs and libraries are, by default, compiled with debugging
   symbols included (with <command>gcc</command>'s <option>-g</option> option).
   This means that when debugging a program or library that was compiled with
@@ -17 +17 @@
   addresses, but also the names of the routines and variables.</para>
 
-  <para>However, the inclusion of these debugging symbols enlarges a
+  <para os="b">However, the inclusion of these debugging symbols enlarges a
   program or library significantly. The following is an example of the
   amount of space these symbols occupy:</para>
 
-  <itemizedlist>
-    <listitem>
+  <itemizedlist os="c">
+    <listitem os="c1">
       <para>a bash binary with debugging symbols: 1200 KB</para>
     </listitem>
-    <listitem>
+    <listitem os="c2">
       <para>a bash binary without debugging symbols: 480 KB</para>
     </listitem>
-    <listitem>
+    <listitem os="c3">
       <para>Glibc and GCC files (<filename class="directory">/lib</filename>
       and <filename class="directory">/usr/lib</filename>) with debugging
       symbols: 87 MB</para>
     </listitem>
-    <listitem>
+    <listitem os="c4">
       <para>Glibc and GCC files without debugging symbols: 16 MB</para>
     </listitem>
   </itemizedlist>
 
-  <para>Sizes may vary depending on which compiler and C library were used,
+  <para os="d">Sizes may vary depending on which compiler and C library were used,
   but when comparing programs with and without debugging symbols, the
   difference will usually be a factor between two and five.</para>
 
-  <para>Because most users will never use a debugger on their system software,
+  <para os="e">Because most users will never use a debugger on their system software,
   a lot of disk space can be regained by removing these symbols. The next
   section shows how to strip all debugging symbols from the programs and

final-system/common/shadow.xml

@@ -105 +105 @@
     etc/login.defs &gt; /etc/login.defs</userinput></screen>
 
-    <para os="r">Move a misplaced program to their proper location:</para>
+    <para os="r">Move a misplaced program to its proper location:</para>
 
 <screen os="s"><userinput>mv /usr/bin/passwd /bin</userinput></screen>

final-system/common/stripping.xml

@@ -11 +11 @@
   <title>Stripping</title>
 
-  <para>If the intended user is not a programmer and does not plan to do
+  <para os="a">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 200 MB by removing the debugging symbols from binaries and
@@ -17 +17 @@
   debug the software fully anymore.</para>
 
-  <para>Most people who use the command mentioned below do not
+  <para os="b">Most people who use the command 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
@@ -23 +23 @@
   backup of the current situation.</para>
 
-  <para>Before performing the stripping, take special care to ensure that
+  <para os="c">Before performing the stripping, take special care to ensure that
   none of the binaries that are about to be stripped are running. If
   unsure whether the user entered chroot with the command given in
@@ -29 +29 @@
   chroot:</para>
 
-<screen><userinput>logout</userinput></screen>
+<screen os="d"><userinput>logout</userinput></screen>
 
-    <para>Then reenter it with:</para>
+    <para os="e">Then reenter it with:</para>
 
-<screen><userinput>chroot $LFS /tools/bin/env -i \
+<screen os="f"><userinput>chroot $LFS /tools/bin/env -i \
     HOME=/root TERM=$TERM PS1='\u:\w\$ ' \
     PATH=/bin:/usr/bin:/sbin:/usr/sbin \
     /tools/bin/bash --login</userinput></screen>
 
-    <para>Now the binaries and libraries can be safely stripped:</para>
+    <para os="g">Now the binaries and libraries can be safely stripped:</para>
 
-<screen><userinput>/tools/bin/find /{,usr/}{bin,lib,sbin} -type f \
+<screen os="h"><userinput>/tools/bin/find /{,usr/}{bin,lib,sbin} -type f \
    -exec /tools/bin/strip --strip-debug '{}' ';'</userinput></screen>
 
-    <para>A large number of files will be reported as having their file
+    <para os="i">A large number of files will be reported as having their file
     format not recognized. These warnings can be safely ignored. These
     warnings indicate that those files are scripts instead of
     binaries.</para>
 
-    <para>If disk space is very tight, the <option>--strip-all</option>
+    <para os="j">If disk space is very tight, the <option>--strip-all</option>
     option can be used on the binaries in <filename
     class="directory">/{,usr/}{bin,sbin}</filename> to gain several more