audience.xml 4.7 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091
  1. <sect1 id="pre-audience">
  2. <title>Audience</title>
  3. <?dbhtml filename="audience.html" dir="preface"?>
  4. <sect2>
  5. <title>Who would want to read this book</title>
  6. <para>There are many reasons why somebody would want to read this book. The
  7. principal reason being to install a Linux system straight from the source
  8. code. A question many people raise is "Why go through all the hassle of
  9. manually building a Linux system from scratch when you can just download and
  10. install an existing one?". That is a good question and is the impetus for this
  11. section of the book.</para>
  12. <para>One important reason for LFS's existence is to help people learn how a
  13. Linux system works from the inside out. Building an LFS system helps demonstrate
  14. to you what makes Linux tick, how things work together and depend on each
  15. other. One of the best things that this learning experience provides is the
  16. ability to customize Linux to your own tastes and needs.</para>
  17. <para>A key benefit of LFS is that you have more control of your system
  18. without relying on someone else's Linux implementation. With LFS, you are
  19. in the driver's seat and dictate every aspect of your system, such as the
  20. directory layout and bootscript setup. You also dictate where, why and how
  21. programs are installed.</para>
  22. <para>Another benefit of LFS is the ability to create a very compact Linux
  23. system. When installing a regular distribution, you are usually forced to
  24. install several programs which you are likely never to use. They're just
  25. sitting there wasting precious disk space (or worse, CPU cycles). It isn't
  26. difficult to build an LFS system less than 100 MB. Does that still sound like a
  27. lot? A few of us have been working on creating a very small embedded LFS
  28. system. We successfully built a system that was just enough to run the Apache
  29. web server with approximately 8MB of disk space used. Further stripping could
  30. bring that down to 5 MB or less. Try that with a regular distribution.</para>
  31. <para>We could compare distributed Linux to a hamburger you buy at a
  32. fast-food restaurant -- you have no idea what you are eating. LFS, on the
  33. other hand, doesn't give you a hamburger, but the recipe to make a hamburger.
  34. This allows you to review it, to omit unwanted ingredients, and to
  35. add your own ingredients which enhance the flavor of your burger. When you
  36. are satisfied with the recipe, you go on to preparing it. You make it just
  37. the way you like it: broil it, bake it, deep-fry it, barbecue it, or eat it
  38. tar-tar (raw).</para>
  39. <para>Another analogy that we can use is that of comparing LFS with a
  40. finished house. LFS will give you the skeletal plan of a house, but it's up
  41. to you to build it. You have the freedom to adjust your plans as you
  42. go.</para>
  43. <para>One last advantage of a custom built Linux system is security.
  44. By compiling the entire system from source code, you are empowered to audit
  45. everything and apply all the security patches you feel are needed. You don't
  46. have to wait for somebody else to compile binary packages that fix a security
  47. hole. Unless you examine the patch and implement it yourself you have no
  48. guarantee that the new binary package was built correctly and actually fixes the
  49. problem (adequately).</para>
  50. <para>There are too many good reasons to build your own LFS system for them all
  51. to be listed here. This section is only the tip of the iceberg. As you
  52. continue in your LFS experience, you will find on your own the power that
  53. information and knowledge truly bring.</para>
  54. </sect2>
  55. <sect2>
  56. <title>Who would not want to read this book</title>
  57. <para>There are probably some, for whatever reason, would feel that they do not
  58. want to read this book. If you do not wish to build your own Linux system from
  59. scratch, then you probably don't want to read this book. Our goal is to help
  60. you build a complete and usable foundation-level system. If you only want to
  61. know what happens while your computer boots, then we recommend the <quote>From
  62. Power Up To Bash Prompt</quote> HOWTO. The HOWTO builds a bare system which is
  63. similar to that of this book, but it focuses strictly on creating a system
  64. capable of booting to a BASH prompt.</para>
  65. <para>While you decide which to read, consider your objective. If you wish
  66. to build a Linux system while learning a bit along the way, then this book
  67. is probably your best choice. If your objective is strictly educational and
  68. you do not have any plans for your finished system, then the
  69. <quote>From Power Up To Bash Prompt</quote> HOWTO is probably a better choice.</para>
  70. <para>The <quote>From Power Up To Bash Prompt</quote> HOWTO is located at
  71. <ulink url="http://axiom.anu.edu.au/~okeefe/p2b/"/> or on The Linux
  72. Documentation Project's website at
  73. <ulink url="http://www.tldp.org/HOWTO/From-PowerUp-To-Bash-Prompt-HOWTO.html"/>.</para>
  74. </sect2>
  75. </sect1>