theend.xml 3.0 KB

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