aboutsummaryrefslogtreecommitdiffstats
path: root/chapter09
diff options
context:
space:
mode:
Diffstat (limited to 'chapter09')
-rw-r--r--chapter09/theend.xml20
1 files changed, 20 insertions, 0 deletions
diff --git a/chapter09/theend.xml b/chapter09/theend.xml
index 8d1111a7b..498a2b176 100644
--- a/chapter09/theend.xml
+++ b/chapter09/theend.xml
@@ -17,6 +17,26 @@ anymore, which is not an issue if you don't know how to debug. You can
remove the symbols by executing the following command:
</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).
+</para>
+
+<para>
+Having that said, the --strip-debug option 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 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>
+
<blockquote><literallayout>
<userinput>find / -type f -exec strip --strip-debug '{}' ';'
</userinput>