mirror of
https://git.linuxfromscratch.org/lfs.git
synced 2025-06-19 11:49:20 +01:00
replaced old 'intro' with current website's introduction
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1078 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
parent
d16f745fe0
commit
22a2710c37
@ -1,23 +1,71 @@
|
|||||||
<sect1 id="pre-whoread">
|
<sect1 id="pre-whoread">
|
||||||
<title>Who would want to read this book</title>
|
<title>Who would want to read this book</title>
|
||||||
|
|
||||||
<para>This book is intended for Linux users who want to setup their own
|
<para>
|
||||||
custom built Linux system. Reasons for wanting to build such a system are
|
There are a lot of reasons why somebody would want to read this book in
|
||||||
diverse. Perhaps you want to get into more detail as to what
|
order to install an LFS system. The question most people raise is "why
|
||||||
happens behind the scenes. Perhaps you are fed up with distributions
|
go through all the hassle of manually installing a Linux system from
|
||||||
which are often bloated or perhaps you don't want to rely on pre-compiled
|
scratch when you can just download an existing version like Debian or
|
||||||
binaries due to security concerns. There are many other reasons why
|
Redhat". That is a valid question which I hope to answer for you.
|
||||||
someone may want a custom built system. If any of these reasons apply to
|
</para>
|
||||||
you, this book is meant for you.</para>
|
|
||||||
|
|
||||||
<para>The fruits of building your own system are plentiful, but the labor may
|
<para>
|
||||||
be hard. There is a long way ahead, but in the end you will be
|
The most important reason for LFS's existence is teaching people how a
|
||||||
able to call yourself the proud owner of your own Linux system,
|
Linux system works internally. Building an LFS system teaches you about
|
||||||
completely tailored after your needs. You will dictate the layout of
|
all that makes Linux tick, how things work together, and depend on each
|
||||||
bootscripts, the file system hierarchy, which programs are installed in
|
other. And most importantly, how to customize it to your own taste and
|
||||||
which directory, which versions of software to use, and more. Perhaps the
|
needs.
|
||||||
most important reason is that you will know exactly what is installed where,
|
</para>
|
||||||
why, and how.</para>
|
|
||||||
|
<para>
|
||||||
|
One of the key benefits of LFS is that you are in control over your
|
||||||
|
system without having to rely on somebody else's Linux implementation
|
||||||
|
like Debian. You are in the driver's seat now and are able to dictate
|
||||||
|
every single thing such as the directory layout and boot script setup.
|
||||||
|
You will also know exactly where, why and how programs are installed.
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
Another benefit of LFS is that you can create a very compact Linux
|
||||||
|
system. When you install a distribution like Debian or RedHat, you end
|
||||||
|
up installing a lot of programs you would never in your life use.
|
||||||
|
They're just sitting there taking up (precious) disk space. It's not
|
||||||
|
hard to get an LFS system installed under 100 MB. Does that still sound
|
||||||
|
like a lot? A few of us have been working on creating a very small
|
||||||
|
embedded LFS system. We installed a system that was just enough to run
|
||||||
|
the Apache web server; total disk space usage was aproximately 8 MB.
|
||||||
|
With further stripping, that can be brought down to 5 MB or less. Try
|
||||||
|
that with a generic Debian or Redhat distribution.
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
If we were to compare a Linux distribution with a hamburger you buy at a
|
||||||
|
supermarket or fast-food restaurant, you would end up eating it without
|
||||||
|
knowing precisely what it is you are eating, whereas LFS gives you the
|
||||||
|
ingredients to make a hamburger. This allows you to carefully inspect
|
||||||
|
it, remove unwanted ingredients, and at the same time allow you to add
|
||||||
|
ingredients to enhance the flavour of your hamburger. When you are
|
||||||
|
satisfied with the ingredients, you go on to the next part of putting it
|
||||||
|
together. You now have the chance to make it just the way you like it:
|
||||||
|
broil it, bake it, deep-fry it, barbeque it, or eat it raw.
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
Another analogy that we can use is that of comparing LFS with a finished
|
||||||
|
house. LFS will give you the skeleton of a house, but it's up to you to
|
||||||
|
install plumbing, electrical outlets, kitchen, bathtub, wallpaper, etc.
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
Another advantage of a custom built Linux system is added security. You
|
||||||
|
will compile the entire system from source, thus allowing you to audit
|
||||||
|
everything, if you wish to do so, and apply all the security patches you
|
||||||
|
want or need to apply. You don't have to wait for somebody else to
|
||||||
|
provide a new binary package that fixes a security hole. Besides, you
|
||||||
|
have no guarantee that the new package actually fixes the problem
|
||||||
|
(adequately). You never truly know whether a security hole is fixed or
|
||||||
|
not unless you do it yourself.
|
||||||
|
</para>
|
||||||
|
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user