gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-06-18 19:29:21 +01:00
Code Issues Packages Projects Releases Wiki Activity

Added some warnings regarding the stripping part

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@648 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Gerard Beekmans 2001-05-21 20:07:20 +00:00
parent 31bb453495
commit f76811f859
1 changed files with 20 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
chapter09/theend.xml
View File

@ -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: remove the symbols by executing the following command:
</para> </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> <blockquote><literallayout>
<userinput>find / -type f -exec strip --strip-debug '{}' ';' <userinput>find / -type f -exec strip --strip-debug '{}' ';'
</userinput> </userinput>