audience.xml 4.8 KB

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