gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-03-06 06:14:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

Removed obsolete commented text, prologue.

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@4591 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Manuel Canales Esparcia 2005-01-30 10:17:04 +00:00
parent 96e5226690
commit 90f6a46980
6 changed files with 1 additions and 222 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

88
prologue/audience.xml
View File

@ -9,92 +9,4 @@
<para>See testing</para> <para>See testing</para>
<!--
<sect2>
<title>Who would want to read this book</title>
<para>There are many reasons why somebody would want to read this book. The
principal reason being to install a Linux system straight from the source
code. A question many people raise is <quote>Why go through all the hassle of
manually building a Linux system from scratch when you can just download and
install an existing one?</quote>. That is a good question and is the impetus for
this section of the book.</para>
<para>One important reason for LFS's existence is to help people learn how a
Linux system works from the inside out. Building an LFS system helps demonstrate
to you what makes Linux tick, how things work together and depend on each
other. One of the best things that this learning experience provides is the
ability to customize Linux to your own tastes and needs.</para>
<para>A key benefit of LFS is that you have more control of your system
without relying on someone else's Linux implementation. With LFS, you are
in the driver's seat and dictate every aspect of your system, such as the
directory layout and bootscript setup. You also dictate where, why and how
programs are installed.</para>
<para>Another benefit of LFS is the ability to create a very compact Linux
system. When installing a regular distribution, you are usually forced to
install several programs which you are likely never to use. They're just
sitting there wasting precious disk space (or worse, CPU cycles). It isn't
difficult to build an LFS system of less than 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 successfully built a system that was just enough to run the Apache
web server with approximately 8MB of disk space used. Further stripping could
bring that down to 5 MB or less. Try that with a regular distribution.</para>
<para>We could compare Linux distributions to a hamburger you buy at a
fast-food restaurant - you have no idea what you are eating. LFS, on the
other hand, doesn't give you a hamburger, but the recipe to make a hamburger.
This allows you to review it, to omit unwanted ingredients, and to
add your own ingredients which enhance the flavor of your burger. When you
are satisfied with the recipe, you go on to preparing it. You make it just
the way you like it: broil it, bake it, deep-fry it, barbecue it, or eat it
tar-tar (raw).</para>
<para>Another analogy that we can use is that of comparing LFS with a
finished house. LFS will give you the skeletal plan of a house, but it's up
to you to build it. You have the freedom to adjust your plans as you
go.</para>
<para>One last advantage of a custom built Linux system is security.
By compiling the entire system from source code, you are empowered to audit
everything and apply all the security patches you feel are needed. You don't
have to wait for somebody else to compile binary packages that fix a security
hole. Unless you examine the patch and implement it yourself you have no
guarantee that the new binary package was built correctly and actually fixes the
problem (adequately).</para>
<para>There are too many good reasons to build your own LFS system for them all
to be listed here. This section is only the tip of the iceberg. As you
continue in your LFS experience, you will find on your own the power that
information and knowledge truly bring.</para>
</sect2>
<sect2>
<title>Who would not want to read this book</title>
<para>There are probably some who, for whatever reason, would feel that they do not
want to read this book. If you do not wish to build your own Linux system from
scratch, then you probably don't want to read this book. Our goal is to help
you build a complete and usable foundation-level system. If you only want to
know what happens while your computer boots, then we recommend the <quote>From
Power Up To Bash Prompt</quote> HOWTO. The HOWTO builds a bare system which is
similar to that of this book, but it focuses strictly on creating a system
capable of booting to a BASH prompt.</para>
<para>While you decide which to read, consider your objective. If you wish
to build a Linux system while learning a bit along the way, then this book
is probably your best choice. If your objective is strictly educational and
you do not have any plans for your finished system, then the
<quote>From Power Up To Bash Prompt</quote> HOWTO is probably a better choice.</para>
<para>The <quote>From Power Up To Bash Prompt</quote> HOWTO is located at
<ulink url="http://axiom.anu.edu.au/~okeefe/p2b/"/> or on The Linux
Documentation Project's website at
<ulink url="http://www.tldp.org/HOWTO/From-PowerUp-To-Bash-Prompt-HOWTO.html"/>.</para>
</sect2>
-->
</sect1> </sect1>

3
prologue/dedication.xml
View File

@ -5,6 +5,5 @@
]> ]>
<dedication> <dedication>
<title>Dedication</title> <title>Dedication</title>
<para>This book is dedicated to my loving and supportive wife <para>This book is dedicated</para>
<emphasis>Beverly Beekmans</emphasis>.</para>
</dedication> </dedication>

24
prologue/foreword.xml
View File

@ -9,28 +9,4 @@
<para>See testing</para> <para>See testing</para>
<!--
<para>Having used a number of different Linux distributions, I was never
fully satisfied with any of them. I didn't like the arrangement of
the bootscripts. I didn't like the way certain programs were configured by
default. Much more of that sort of thing bothered me. Finally I realized
that if I wanted full satisfaction from my Linux system I would have to
build my own system from scratch, using only the source code. I resolved
not to use pre-compiled packages of any kind, nor CD-ROM or boot disk that
would install some basic utilities. I would use my current Linux system to
develop my own.</para>
<para>This wild idea seemed very difficult at the time and often seemed
an impossible task. After sorting out all kinds of problems, such as
dependencies and compile-time errors, a custom-built Linux system was
created that was fully operational. I called this system a Linux From Scratch
system, or LFS for short.</para>
<para>I hope you will have a great time working on your own LFS!</para>
<literallayout>-
Gerard Beekmans
gerard@linuxfromscratch.org</literallayout>
-->
</sect1> </sect1>

30
prologue/organization.xml
View File

@ -9,34 +9,4 @@
<para>See testing</para> <para>See testing</para>
<!--
<para>This book is divided into the following parts:</para>
<sect2>
<title>Part I - Introduction</title>
<para>Part I explains a few important things on how to proceed with the
installation, and gives meta-information about the book (version, changelog,
acknowledgments, associated mailing lists, and so on).</para>
</sect2>
<sect2>
<title>Part II - Preparing for the build</title>
<para>Part II describes how to prepare for the building process: making a
partition, downloading the packages, and compiling temporary tools.</para>
</sect2>
<sect2>
<title>Part III - Building the LFS system</title>
<para>Part III guides you through the building of the LFS system: compiling and
installing all the packages one by one, setting up the boot scripts, and
installing the kernel. The resulting basic Linux system is the foundation upon
which you can build other software, to extend your system in the way you like.
At the end of the book you'll find a list of all of the programs, libraries and
important files that have been installed as an easy to use reference.</para>
</sect2>
-->
</sect1> </sect1>

32
prologue/prerequisites.xml
View File

@ -9,36 +9,4 @@
<para>See testing</para> <para>See testing</para>
<!--
<para>This book assumes that its reader has a good deal of knowledge about
using and installing Linux software. Before you begin building your LFS
system, you should read the following HOWTOs:</para>
<itemizedlist>
<listitem><para>Software-Building-HOWTO</para>
<para>This is a comprehensive guide to building and installing
<quote>generic</quote> Unix software distributions under Linux. This HOWTO is
available at <ulink
url="http://www.tldp.org/HOWTO/Software-Building-HOWTO.html"/>.</para>
</listitem>
<listitem><para>The Linux Users' Guide</para>
<para>This guide covers the usage of assorted Linux software and is
available at
<ulink url="http://espc22.murdoch.edu.au/~stewart/guide/guide.html"/>.</para></listitem>
<listitem><para>The Essential Pre-Reading Hint</para>
<para>This is an LFS Hint written specifically for new users of Linux. It is
mostly a list of links to excellent sources of information on a wide range of
topics. Any person attempting to install LFS, should at least have an
understanding of many of the topics in this hint. It is available at
<ulink url="&hints-root;essential_prereading.txt"/></para></listitem>
</itemizedlist>
-->
</sect1> </sect1>

46
prologue/typography.xml
View File

@ -9,50 +9,4 @@
<para>See testing</para> <para>See testing</para>
<!--
<para>To make things easier to follow, there are a few typographical
conventions used throughout the book. Following are some examples:</para>
<screen><userinput>./configure -prefix=/usr</userinput></screen>
<blockquote><para>This form of text is designed to be typed exactly
as seen unless otherwise noted in the surrounding text. It is also used
in the explanation sections to identify which of the commands is being
referenced.</para></blockquote>
<screen><computeroutput>install-info: unknown option `-dir-file=/mnt/lfs/usr/info/dir'</computeroutput></screen>
<blockquote><para>This form of text (fixed width text) is showing screen
output, probably as the result of commands issued, and is also used to
show filenames, such as <filename>/etc/ld.so.conf</filename>.</para></blockquote>
<para><emphasis>Emphasis</emphasis></para>
<blockquote><para>This form of text is used for several purposes in the
book, mainly to emphasize important points or items.</para></blockquote>
<para><ulink url="&lfs-root;"/></para>
<blockquote><para>This form of text is used for hyperlinks, both within the
book and to external pages such as HOWTOs, download locations and
websites.</para></blockquote>
<screen><userinput>cat &gt; $LFS/etc/group &lt;&lt; "EOF"
root:x:0:
bin:x:1:
......
EOF</userinput></screen>
<blockquote><para>This type of section is used mainly when creating
configuration files. The first command tells the system to create
the file <filename>$LFS/etc/group</filename> from whatever is typed on the following lines until
the sequence EOF is encountered. Therefore, this whole section is generally
typed as seen.</para></blockquote>
<para><replaceable>[REPLACED TEXT]</replaceable></para>
<blockquote><para>This form of text is used to encapsulate text that is
not to be typed as seen or copy and pasted.</para></blockquote>
-->
</sect1> </sect1>