diff options
| author | Gerard Beekmans <gerard@linuxfromscratch.org> | 2001-05-21 20:07:20 +0000 |
|---|---|---|
| committer | Gerard Beekmans <gerard@linuxfromscratch.org> | 2001-05-21 20:07:20 +0000 |
| commit | f76811f859f794b788567a916baf8457090f77f1 (patch) | |
| tree | de36a92beb516798863314bf67083026c9826eca /chapter09 | |
| parent | 31bb453495a7ae85d0cd957f2d1bd1aff3bf5183 (diff) | |
Added some warnings regarding the stripping part
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@648 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter09')
| -rw-r--r-- | chapter09/theend.xml | 20 |
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 & 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> |