source: preface/whoread.xml@ 7c1805bb

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.0 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 v4_0 v4_1 v5_0 v5_1 v5_1_1 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 7c1805bb was fd49733, checked in by Gerard Beekmans <gerard@…>, 22 years ago

removed distro specific names

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

  • Property mode set to 100644
File size: 3.1 KB
Line 
1<sect1 id="pre-whoread">
2<title>Who would want to read this book</title>
3<?dbhtml filename="whoread.html" dir="preface"?>
4
5<para>There are a lot of reasons why somebody would want to read this
6book in order to install an LFS system. The question most people raise
7is "why go through all the hassle of manually installing a Linux system
8from scratch when you can just download an existing distribution?". That is
9a valid question which I hope to answer for you.</para>
10
11<para>The most important reason for LFS's existence is teaching people
12how a Linux system works internally. Building an LFS system teaches you
13about all that makes Linux tick, how things work together, and depend on
14each other. And most importantly, how to customize it to your own taste
15and needs.</para>
16
17<para>One of the key benefits of LFS is that you are in control of
18your system without having to rely on somebody else's Linux
19implementation. You are in the driver's seat now and are
20able to dictate every single thing such as the directory layout and boot
21script setup. You will also know exactly where, why and how programs
22are installed.</para>
23
24<para>Another benefit of LFS is that you can create a very compact Linux
25system. When you install a regular distribution, you end
26up installing a lot of programs you probably would never use.
27They're just sitting there taking up (precious) disk space. It's not
28hard to get an LFS system installed under 100 MB. Does that still sound
29like a lot? A few of us have been working on creating a very small
30embedded LFS system. We installed a system that was just enough to run
31the Apache web server; total disk space usage was approximately 8 MB.
32With further stripping, that can be brought down to 5 MB or less. Try
33that with a regular distribution.</para>
34
35<para>If we were to compare a Linux distribution with a hamburger you
36buy at a supermarket or fast-food restaurant, you would end up eating it
37without knowing precisely what it is you are eating, whereas LFS gives
38you the ingredients to make a hamburger. This allows you to carefully
39inspect it, remove unwanted ingredients, and at the same time allow you
40to add ingredients to enhance the flavour of your hamburger. When you are
41satisfied with the ingredients, you go on to the next part of putting it
42together. You now have the chance to make it just the way you like it:
43broil it, bake it, deep-fry it, barbeque it, or eat it raw.</para>
44
45<para>Another analogy that we can use is that of comparing LFS with a
46finished house. LFS will give you the skeleton of a house, but it's up
47to you to install plumbing, electrical outlets, kitchen, bathtub,
48wallpaper, etc.</para>
49
50<para>Another advantage of a custom built Linux system is added security.
51You will compile the entire system from source, thus allowing you to audit
52everything, if you wish to do so, and apply all the security patches you
53want or need to apply. You don't have to wait for somebody else to
54provide a new binary package that fixes a security hole. Besides, you
55have no guarantee that the new package actually fixes the problem
56(adequately). You never truly know whether a security hole is fixed or
57not unless you do it yourself.</para>
58
59</sect1>
60
Note: See TracBrowser for help on using the repository browser.