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