[e0f737f] | 1 | <sect1 id="ch09-theend">
|
---|
[6acc848] | 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 |
|
---|
[921d418f] | 10 | <para>
|
---|
[640c87f] | 11 | Now would be a good time to strip all debug symbols from
|
---|
[e3a1c58] | 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:
|
---|
[921d418f] | 18 | </para>
|
---|
| 19 |
|
---|
[f76811f] | 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 |
|
---|
[3229c6b] | 40 | <para>
|
---|
| 41 | <screen>
|
---|
| 42 | <userinput>find / -type f -exec strip --strip-debug '{}' ';'</userinput>
|
---|
| 43 | </screen>
|
---|
| 44 | </para>
|
---|
[921d418f] | 45 |
|
---|
[6acc848] | 46 | <para>
|
---|
| 47 | If you plan to ever upgrade to a newer LFS version in the future it
|
---|
| 48 | will be a good idea to create the /etc/lfs-&version; file. By having
|
---|
| 49 | this file it is very easy for you (and for us if you are going to ask
|
---|
| 50 | for help with something at some point) to find out which LFS version
|
---|
| 51 | you have installed on your system. This can just be a null-byte file by
|
---|
[5a01e43] | 52 | running:
|
---|
[6acc848] | 53 | </para>
|
---|
| 54 |
|
---|
[3229c6b] | 55 | <para>
|
---|
| 56 | <screen>
|
---|
| 57 | <userinput>touch /etc/lfs-&version;</userinput>
|
---|
| 58 | </screen>
|
---|
| 59 | </para>
|
---|
[5a01e43] | 60 |
|
---|
[e0f737f] | 61 | <para>
|
---|
| 62 | One final thing you may want to do is run lilo now that you are booted
|
---|
| 63 | into LFS. This way you will put the LFS version of LILO in the MBR
|
---|
| 64 | rather than the one that's there right now from your host system.
|
---|
| 65 | Depending on how old your host distribution is, the LFS version may have
|
---|
| 66 | more advanced features you need/could use.
|
---|
| 67 | </para>
|
---|
| 68 |
|
---|
| 69 | <para>
|
---|
| 70 | Either way, run the following to make the lilo version installed on LFS
|
---|
| 71 | active:
|
---|
| 72 | </para>
|
---|
| 73 |
|
---|
[3229c6b] | 74 | <para>
|
---|
| 75 | <screen>
|
---|
| 76 | <userinput>/sbin/lilo</userinput>
|
---|
| 77 | </screen>
|
---|
| 78 | </para>
|
---|
[e0f737f] | 79 |
|
---|
[9a0cfdf] | 80 | <para>
|
---|
| 81 | If you are wondering: "Well, where to go now?" you'll be glad to hear that
|
---|
[b4ffa369] | 82 | someone has written an LFS hint on the subject at <ulink
|
---|
| 83 | url="http://archive.linuxfromscratch.org/lfs-hints/afterlfs.txt">
|
---|
| 84 | http://archive.linuxfromscratch.org/lfs-hints/afterlfs.txt</ulink>.
|
---|
| 85 | On a same note, if you are not only newbie to LFS, but also
|
---|
| 86 | newbie to Linux in general, you may find the newbie hint at <ulink
|
---|
| 87 | url="http://archive.linuxfromscratch.org/lfs-hints/newbie.txt">
|
---|
| 88 | http://archive.linuxfromscratch.org/lfs-hints/newbie.txt</ulink>
|
---|
| 89 | very interesting.
|
---|
[9a0cfdf] | 90 | </para>
|
---|
| 91 |
|
---|
[6acc848] | 92 | <para>
|
---|
[9c86d3c] | 93 | Don't forget there are several LFS mailinglists you can subscribe to if
|
---|
[6acc848] | 94 | you are in need of help, advice, etc. See
|
---|
| 95 | <ulink url="ch01-maillists.html">Chapter 1 - Mailinglists</ulink> for
|
---|
| 96 | more information.
|
---|
| 97 | </para>
|
---|
| 98 |
|
---|
| 99 | <para>
|
---|
| 100 | Again, we thank you for using the LFS Book and hope you found this book
|
---|
| 101 | useful and worth your time.
|
---|
| 102 | </para>
|
---|
| 103 |
|
---|
| 104 | </sect1>
|
---|
| 105 |
|
---|