source: chapter09/theend.xml@ 640c87f

10.0 10.0-rc1 10.1 10.1-rc1 11.0 11.0-rc1 11.0-rc2 11.0-rc3 11.1 11.1-rc1 11.2 11.2-rc1 11.3 11.3-rc1 12.0 12.0-rc1 12.1 12.1-rc1 6.0 6.1 6.1.1 6.3 6.4 6.5 6.6 6.7 6.8 7.0 7.1 7.2 7.3 7.4 7.5 7.5-systemd 7.6 7.6-systemd 7.7 7.7-systemd 7.8 7.8-systemd 7.9 7.9-systemd 8.0 8.1 8.2 8.3 8.4 9.0 9.1 arm bdubbs/gcc13 ml-11.0 multilib renodr/libudev-from-systemd s6-init trunk v3_0 v3_1 v3_2 v3_3 v4_0 v4_1 v5_0 v5_1 v5_1_1 xry111/arm64 xry111/arm64-12.0 xry111/clfs-ng xry111/lfs-next xry111/loongarch xry111/loongarch-12.0 xry111/loongarch-12.1 xry111/mips64el xry111/pip3 xry111/rust-wip-20221008 xry111/update-glibc
Last change on this file since 640c87f was 640c87f, checked in by Gerard Beekmans <gerard@…>, 23 years ago

Changed --strip-unneeded to --strip-debug
According to a report --strip-unneeded isn't as safe on libraries as we
originally thought it to be. Apparently it will cause static link
failures when static libs are stripped that way. Dynamic libs may have
some unexpected problems too.

So we'll just go back on the safe side and only use --strip-debug

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@637 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

  • Property mode set to 100644
File size: 2.1 KB
Line 
1<sect1 id="ch10-theend">
2<title>The End</title>
3
4<para>
5Well done! You have finished installing your LFS system. It may have
6been a long process but it was well worth it. We wish you a lot of fun
7with your new shiny custom built Linux system.
8</para>
9
10<para>
11Now would be a good time to strip all debug symbols from
12the binaries on your LFS system. If you are not a programmer and don't plan
13on debugging your software, then you will be happy to know that you can
14reclaim a few tens of megs by removing debug symbols. This process causes
15no inconvenience other than not being able to debug the software fully
16anymore, which is not an issue if you don't know how to debug. You can
17remove the symbols by executing the following command:
18</para>
19
20<blockquote><literallayout>
21 <userinput>find / -type f -exec strip --strip-debug '{}' ';'
22 </userinput>
23</literallayout></blockquote>
24
25<para>
26If you plan to ever upgrade to a newer LFS version in the future it
27will be a good idea to create the /etc/lfs-&version; file. By having
28this file it is very easy for you (and for us if you are going to ask
29for help with something at some point) to find out which LFS version
30you have installed on your system. This can just be a null-byte file by
31running:
32</para>
33
34<blockquote><literallayout>
35 <userinput>touch /etc/lfs-&version;</userinput>
36</literallayout></blockquote>
37
38<para>
39If you are wondering: "Well, where to go now?" you'll be glad to hear that
40someone has written an <ulink
41url="http://archive.linuxfromscratch.org/lfs-hints/Afterlfs.txt">LFS-Hint</ulink>
42on that subject. On a same note, if you are not only newbie to LFS, but also
43newbie to Linux in general, you may find the <ulink
44url="http://archive.linuxfromscratch.org/lfs-hints/newbie.txt">newbie
45hint</ulink> very interesting.
46</para>
47
48<para>
49Don't forget there are several LFS mailinglists you can subscribe to if
50you are in need of help, advice, etc. See
51<ulink url="ch01-maillists.html">Chapter 1 - Mailinglists</ulink> for
52more information.
53</para>
54
55<para>
56Again, we thank you for using the LFS Book and hope you found this book
57useful and worth your time.
58</para>
59
60</sect1>
61
Note: See TracBrowser for help on using the repository browser.