1 | <sect1 id="ch10-theend">
|
---|
2 | <title>The End</title>
|
---|
3 |
|
---|
4 | <para>
|
---|
5 | Well done! You have finished installing your LFS system. It may have
|
---|
6 | been a long process but it was well worth it. We wish you a lot of fun
|
---|
7 | with your new shiny custom built Linux system.
|
---|
8 | </para>
|
---|
9 |
|
---|
10 | <para>
|
---|
11 | Now would be a good time to strip all debug symbols from
|
---|
12 | the binaries on your LFS system. If you are not a programmer and don't plan
|
---|
13 | on debugging your software, then you will be happy to know that you can
|
---|
14 | reclaim a few tens of megs by removing debug symbols. This process causes
|
---|
15 | no inconvenience other than not being able to debug the software fully
|
---|
16 | anymore, which is not an issue if you don't know how to debug. You can
|
---|
17 | remove the symbols by executing the following command:
|
---|
18 | </para>
|
---|
19 |
|
---|
20 | <para>
|
---|
21 | Disclaimer: 98% of the people who use the command mentioned below don't
|
---|
22 | experience any problems. But do make a backup of your LFS system before
|
---|
23 | you run this command. There's a slight chance it may backfire on you and
|
---|
24 | render your system unusable (mostly by destroying your kernel modules
|
---|
25 | and dynamic & shared libraries).
|
---|
26 | </para>
|
---|
27 |
|
---|
28 | <para>
|
---|
29 | Having that said, the --strip-debug option to strip is quite harmless
|
---|
30 | under normal circumstances. It doesn't strip anything vital from the
|
---|
31 | files. It also is quite safe to use --strip-all on regular programs
|
---|
32 | (don't use that on libraries - they will be destroyed) but it's not as
|
---|
33 | safe and the space you gain is not all that much. But if you're tight on
|
---|
34 | disk space every little bit helps, so decide yourself. Please refer to
|
---|
35 | the strip man page for other strip options you can use. The general idea
|
---|
36 | is to not run strip on libraries (other than --strip-debug) just to be
|
---|
37 | on the safe side.
|
---|
38 | </para>
|
---|
39 |
|
---|
40 | <blockquote><literallayout>
|
---|
41 | <userinput>find / -type f -exec strip --strip-debug '{}' ';'
|
---|
42 | </userinput>
|
---|
43 | </literallayout></blockquote>
|
---|
44 |
|
---|
45 | <para>
|
---|
46 | If you plan to ever upgrade to a newer LFS version in the future it
|
---|
47 | will be a good idea to create the /etc/lfs-&version; file. By having
|
---|
48 | this file it is very easy for you (and for us if you are going to ask
|
---|
49 | for help with something at some point) to find out which LFS version
|
---|
50 | you have installed on your system. This can just be a null-byte file by
|
---|
51 | running:
|
---|
52 | </para>
|
---|
53 |
|
---|
54 | <blockquote><literallayout>
|
---|
55 | <userinput>touch /etc/lfs-&version;</userinput>
|
---|
56 | </literallayout></blockquote>
|
---|
57 |
|
---|
58 | <para>
|
---|
59 | If you are wondering: "Well, where to go now?" you'll be glad to hear that
|
---|
60 | someone has written an <ulink
|
---|
61 | url="http://archive.linuxfromscratch.org/lfs-hints/Afterlfs.txt">LFS-Hint</ulink>
|
---|
62 | on that subject. On a same note, if you are not only newbie to LFS, but also
|
---|
63 | newbie to Linux in general, you may find the <ulink
|
---|
64 | url="http://archive.linuxfromscratch.org/lfs-hints/newbie.txt">newbie
|
---|
65 | hint</ulink> very interesting.
|
---|
66 | </para>
|
---|
67 |
|
---|
68 | <para>
|
---|
69 | Don't forget there are several LFS mailinglists you can subscribe to if
|
---|
70 | you are in need of help, advice, etc. See
|
---|
71 | <ulink url="ch01-maillists.html">Chapter 1 - Mailinglists</ulink> for
|
---|
72 | more information.
|
---|
73 | </para>
|
---|
74 |
|
---|
75 | <para>
|
---|
76 | Again, we thank you for using the LFS Book and hope you found this book
|
---|
77 | useful and worth your time.
|
---|
78 | </para>
|
---|
79 |
|
---|
80 | </sect1>
|
---|
81 |
|
---|