audience.xml 4.6 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091
  1. <?xml version="1.0" encoding="ISO-8859-1"?>
  2. <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
  3. <!ENTITY % general-entities SYSTEM "../general.ent">
  4. %general-entities;
  5. ]>
  6. <sect1 id="pre-audience">
  7. <title>Audience</title>
  8. <?dbhtml filename="audience.html"?>
  9. <para>There are many reasons why somebody would want to read this
  10. book. The principal reason is to install a Linux system
  11. from the source code. A question many people raise is, <quote>why go
  12. through all the hassle of manually building a Linux system from
  13. scratch when you can just download and install an existing
  14. one?</quote> That is a good question and is the impetus for this
  15. section of the book.</para>
  16. <para>One important reason for LFS's existence is to help people learn
  17. how a Linux system works from the inside out. Building an LFS system
  18. helps demonstrate what makes Linux tick, and how things work together
  19. and depend on each other. One of the best things that this learning
  20. experience provides is the ability to customize Linux to your own
  21. tastes and needs.</para>
  22. <para>A key benefit of LFS is that it allows users to have more
  23. control over the system without relying on someone else's Linux
  24. implementation. With LFS, <emphasis>you</emphasis> are in the
  25. driver's seat and dictate every aspect of the system, such as the
  26. directory layout and bootscript setup. You also dictate where, why,
  27. and how programs are installed.</para>
  28. <para>Another benefit of LFS is the ability to create a very compact
  29. Linux system. When installing a regular distribution, one is often
  30. forced to include several programs which are probably never used.
  31. These programs waste disk space, or worse, CPU cycles. It is
  32. not difficult to build an LFS system of less than 100 megabytes (MB),
  33. which is substantially smaller than the majority of existing installations. Does
  34. this still sound like a lot of space? A few of us have been working on
  35. creating a very small embedded LFS system. We successfully built a
  36. system that was specialized to run the Apache web server with
  37. approximately 8MB of disk space used. Further stripping could bring
  38. this down to 5 MB or less. Try that with a regular distribution!
  39. This is only one of the many benefits of designing your own Linux
  40. implementation.</para>
  41. <para>We could compare Linux distributions to a hamburger purchased at
  42. a fast-food restaurant&mdash;you have no idea what might be in what
  43. you are eating. LFS, on the other hand, does not give you a hamburger.
  44. Rather, LFS provides the recipe to make the exact hamburger desired.
  45. This allows users to review the recipe, omit unwanted ingredients, and
  46. add your own ingredients to enhance the flavor of the burger.
  47. When you are satisfied with the recipe, move on to preparing it. It
  48. can be made to exact specifications&mdash;broil it, bake it, deep-fry
  49. it, or barbecue it.</para>
  50. <para>Another analogy that we can use is that of comparing LFS with a
  51. finished house. LFS provides the skeletal plan of a house, but it is up
  52. to you to build it. LFS maintains the freedom to adjust plans
  53. throughout the process, customizing it to the user's needs and
  54. preferences.</para>
  55. <para>An additional advantage of a custom built Linux system is
  56. security. By compiling the entire system from source code, you are
  57. empowered to audit everything and apply all the security patches
  58. desired. It is no longer necessary to wait for somebody else to
  59. compile binary packages that fix a security hole. Unless you
  60. examine the patch and implement it yourself, you have no guarantee
  61. that the new binary package was built correctly and adequately fixes
  62. the problem.</para>
  63. <para>The goal of Linux From Scratch is to build a complete and usable
  64. foundation-level system. Readers who do not wish to build their own
  65. Linux system from scratch may not benefit from the information in this
  66. book. If you only want to know what happens while the computer boots,
  67. we recommend the <quote>From Power Up To Bash Prompt</quote> HOWTO
  68. located at <ulink url="http://axiom.anu.edu.au/~okeefe/p2b/"/> or on
  69. The Linux Documentation Project's (TLDP) website at <ulink
  70. url="http://www.tldp.org/HOWTO/From-PowerUp-To-Bash-Prompt-HOWTO.html"/>.
  71. The HOWTO builds a system which is similar to that of this book,
  72. but it focuses strictly on creating a system capable of booting to a
  73. BASH prompt. Consider your objective. If you wish to build a Linux
  74. system while learning along the way, then this book is your best
  75. choice.</para>
  76. <para>There are too many good reasons to build your own LFS system to
  77. list them all here. This section is only the tip of the iceberg. As
  78. you continue in your LFS experience, you will find the power that
  79. information and knowledge truly bring.</para>
  80. </sect1>