source: prologue/audience.xml@ 81fd230

10.0 10.0-rc1 10.1 10.1-rc1 11.0 11.0-rc1 11.0-rc2 11.0-rc3 11.1 11.1-rc1 11.2 11.2-rc1 11.3 11.3-rc1 12.0 12.0-rc1 12.1 12.1-rc1 6.1 6.1.1 6.3 6.4 6.5 6.6 6.7 6.8 7.0 7.1 7.2 7.3 7.4 7.5 7.5-systemd 7.6 7.6-systemd 7.7 7.7-systemd 7.8 7.8-systemd 7.9 7.9-systemd 8.0 8.1 8.2 8.3 8.4 9.0 9.1 arm bdubbs/gcc13 ml-11.0 multilib renodr/libudev-from-systemd s6-init trunk xry111/arm64 xry111/arm64-12.0 xry111/clfs-ng xry111/lfs-next xry111/loongarch xry111/loongarch-12.0 xry111/loongarch-12.1 xry111/mips64el xry111/pip3 xry111/rust-wip-20221008 xry111/update-glibc
Last change on this file since 81fd230 was 81fd230, checked in by Gerard Beekmans <gerard@…>, 19 years ago

Trunk is now identical to Testing

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@4648 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

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