source: BOOK/prologue/common/audience.xml @ 07621da

clfs-1.2clfs-2.1clfs-3.0.0-systemdclfs-3.0.0-sysvinitsystemdsysvinit
Last change on this file since 07621da was 07621da, checked in by Chris Staub <chris@…>, 17 years ago

Text updates, and addition of a clfs-wiki entity to account for the difference between the CLFS trac website and the package/patch download site

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