whoread.xml 3.0 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556
  1. <sect1 id="pre-whoread">
  2. <title>Who would want to read this book</title>
  3. <?dbhtml filename="whoread.html" dir="preface"?>
  4. <para>There are many reasons why somebody would want to read this book. The
  5. principle reason being to install an LFS system. A question many people raise
  6. is "Why go through all the hassle of manually building a Linux system
  7. from scratch when you can just download and install an existing one?". That
  8. is a good question.</para>
  9. <para>One important reason for LFS's existence is helping people
  10. learn how a Linux system works from the inside out. Building an LFS system
  11. helps demonstrate what makes Linux tick, and how things work together and
  12. depend on each other. And perhaps most importantly, how to customize it to
  13. your own tastes and needs.</para>
  14. <para>A key benefit of LFS is that you have more control of your system
  15. without relying on someone else's Linux implementation. With LFS, you are
  16. in the driver's seat and dictate every aspect of your system, such as the
  17. directory layout and boot script setup. You also dictate where, why and how
  18. programs are installed.</para>
  19. <para>Another benefit of LFS is the ability to create a very compact Linux
  20. system. When installing a regular distribution, you end up with a lot of
  21. programs you likely will never use. They're just sitting there wasting
  22. (precious) disk space. It isn't difficult to build LFS systems of under
  23. 100 MB. Does that still sound like a lot? A few of us have been working on
  24. creating a very small embedded LFS system. We successfully built a system
  25. that was just enough to run the Apache web server with approximately 8MB
  26. of disk space used. Further stripping could bring that down to 5 MB or
  27. less. Try that with a regular distribution.</para>
  28. <para>We could compare distributed Linux to a hamburger you buy at a
  29. fast-food restaurant. You have no idea what you are easting. LFS on the
  30. other hand, doesn't give you a hamburger, but the recipe to make a hamburger.
  31. This allows you to review it, omit unwanted ingredients, and allows you to
  32. add your own ingredients that enhance the flavor of your burger. When you
  33. are satisfied with the recipe, you go on to preparing it. You make it just
  34. the way you like it: broil it, bake it, deep-fry it, barbeque it, or eat it
  35. tar-tar (raw).</para>
  36. <para>Another analogy that we can use is that of comparing LFS with a
  37. finished house. LFS will give you the skeletal plan of a house, but it's up
  38. to you to build it, giving you the freedom to adjust your plans as you go.</para>
  39. <para>Another advantage of a custom built Linux system is security.
  40. By compiling the entire system from source code, you are empowered to audit
  41. everything and apply all the security patches you feel are needed. You don't
  42. have to wait for somebody else to compile binary packages that fix a security
  43. hole. Examine the new patch and build it yourself. You have no guarantee
  44. that the new package was built correctly and actually fixes the problem
  45. (adequately). You never truly know whether a security hole is fixed or
  46. not unless you do it yourself.</para>
  47. </sect1>