Changeset 90f6a46


Ignore:
Timestamp:
01/30/2005 10:17:04 AM (19 years ago)
Author:
Manuel Canales Esparcia <manuel@…>
Branches:
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
Children:
a460953
Parents:
96e5226
Message:

Removed obsolete commented text, prologue.

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

Location:
prologue
Files:
6 edited

Legend:

Unmodified
Added
Removed

  • prologue/audience.xml

    r96e5226 r90f6a46  
    1010<para>See testing</para>
    1111
    12 <!--
    13 <sect2>
    14 <title>Who would want to read this book</title>
    15 
    16 <para>There are many reasons why somebody would want to read this book. The
    17 principal reason being to install a Linux system straight from the source
    18 code. A question many people raise is <quote>Why go through all the hassle of
    19 manually building a Linux system from scratch when you can just download and
    20 install an existing one?</quote>. That is a good question and is the impetus for
    21 this section of the book.</para>
    22 
    23 <para>One important reason for LFS's existence is to help people learn how a
    24 Linux system works from the inside out. Building an LFS system helps demonstrate
    25 to you what makes Linux tick, how things work together and depend on each
    26 other. One of the best things that this learning experience provides is the
    27 ability to customize Linux to your own tastes and needs.</para>
    28 
    29 <para>A key benefit of LFS is that you have more control of your system
    30 without relying on someone else's Linux implementation. With LFS, you are
    31 in the driver's seat and dictate every aspect of your system, such as the
    32 directory layout and bootscript setup. You also dictate where, why and how
    33 programs are installed.</para>
    34 
    35 <para>Another benefit of LFS is the ability to create a very compact Linux
    36 system. When installing a regular distribution, you are usually forced to
    37 install several programs which you are likely never to use. They're just
    38 sitting there wasting precious disk space (or worse, CPU cycles). It isn't
    39 difficult to build an LFS system of less than 100 MB. Does that still sound like a
    40 lot? A few of us have been working on creating a very small embedded LFS
    41 system. We successfully built a system that was just enough to run the Apache
    42 web server with approximately 8MB of disk space used. Further stripping could
    43 bring that down to 5 MB or less. Try that with a regular distribution.</para>
    44 
    45 <para>We could compare Linux distributions to a hamburger you buy at a
    46 fast-food restaurant - you have no idea what you are eating. LFS, on the
    47 other hand, doesn't give you a hamburger, but the recipe to make a hamburger.
    48 This allows you to review it, to omit unwanted ingredients, and to
    49 add your own ingredients which enhance the flavor of your burger. When you
    50 are satisfied with the recipe, you go on to preparing it. You make it just
    51 the way you like it: broil it, bake it, deep-fry it, barbecue it, or eat it
    52 tar-tar (raw).</para>
    53 
    54 <para>Another analogy that we can use is that of comparing LFS with a
    55 finished house. LFS will give you the skeletal plan of a house, but it's up
    56 to you to build it. You have the freedom to adjust your plans as you
    57 go.</para>
    58 
    59 <para>One last advantage of a custom built Linux system is security.
    60 By compiling the entire system from source code, you are empowered to audit
    61 everything and apply all the security patches you feel are needed. You don't
    62 have to wait for somebody else to compile binary packages that fix a security
    63 hole. Unless you examine the patch and implement it yourself you have no
    64 guarantee that the new binary package was built correctly and actually fixes the
    65 problem (adequately).</para>
    66 
    67 <para>There are too many good reasons to build your own LFS system for them all
    68 to be listed here. This section is only the tip of the iceberg.  As you
    69 continue in your LFS experience, you will find on your own the power that
    70 information and knowledge truly bring.</para>
    71 
    72 </sect2>
    73 
    74 <sect2>
    75 <title>Who would not want to read this book</title>
    76 
    77 <para>There are probably some who, for whatever reason, would feel that they do not
    78 want to read this book. If you do not wish to build your own Linux system from
    79 scratch, then you probably don't want to read this book. Our goal is to help
    80 you build a complete and usable foundation-level system. If you only want to
    81 know what happens while your computer boots, then we recommend the <quote>From
    82 Power Up To Bash Prompt</quote> HOWTO. The HOWTO builds a bare system which is
    83 similar to that of this book, but it focuses strictly on creating a system
    84 capable of booting to a BASH prompt.</para>
    85 
    86 <para>While you decide which to read, consider your objective. If you wish
    87 to build a Linux system while learning a bit along the way, then this book
    88 is probably your best choice. If your objective is strictly educational and
    89 you do not have any plans for your finished system, then the
    90 <quote>From Power Up To Bash Prompt</quote> HOWTO is probably a better choice.</para>
    91 
    92 <para>The <quote>From Power Up To Bash Prompt</quote> HOWTO is located at
    93 <ulink url="http://axiom.anu.edu.au/~okeefe/p2b/"/> or on The Linux
    94 Documentation Project's website at
    95 <ulink url="http://www.tldp.org/HOWTO/From-PowerUp-To-Bash-Prompt-HOWTO.html"/>.</para>
    96 
    97 </sect2>
    98 -->
    99 
    10012</sect1>

  • prologue/dedication.xml

    r96e5226 r90f6a46  
    66<dedication>
    77<title>Dedication</title>
    8 <para>This book is dedicated to my loving and supportive wife
    9 <emphasis>Beverly Beekmans</emphasis>.</para>
     8<para>This book is dedicated</para>
    109</dedication>

  • prologue/foreword.xml

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

  • prologue/organization.xml

    r96e5226 r90f6a46  
    1010<para>See testing</para>
    1111
    12 <!--
    13 <para>This book is divided into the following parts:</para>
    14 
    15 <sect2>
    16 <title>Part I - Introduction</title>
    17 
    18 <para>Part I explains a few important things on how to proceed with the
    19 installation, and gives meta-information about the book (version, changelog,
    20 acknowledgments, associated mailing lists, and so on).</para>
    21 </sect2>
    22 
    23 <sect2>
    24 <title>Part II - Preparing for the build</title>
    25 
    26 <para>Part II describes how to prepare for the building process: making a
    27 partition, downloading the packages, and compiling temporary tools.</para>
    28 </sect2>
    29 
    30 <sect2>
    31 <title>Part III - Building the LFS system</title>
    32 
    33 <para>Part III guides you through the building of the LFS system: compiling and
    34 installing all the packages one by one, setting up the boot scripts, and
    35 installing the kernel. The resulting basic Linux system is the foundation upon
    36 which you can build other software, to extend your system in the way you like.
    37 At the end of the book you'll find a list of all of the programs, libraries and
    38 important files that have been installed as an easy to use reference.</para>
    39 </sect2>
    40 -->
    41 
    4212</sect1>

  • prologue/prerequisites.xml

    r96e5226 r90f6a46  
    1010<para>See testing</para>
    1111
    12 <!--
    13 <para>This book assumes that its reader has a good deal of knowledge about
    14 using and installing Linux software. Before you begin building your LFS
    15 system, you should read the following HOWTOs:</para>
    16 
    17 <itemizedlist>
    18 <listitem><para>Software-Building-HOWTO</para>
    19 
    20 <para>This is a comprehensive guide to building and installing
    21 <quote>generic</quote> Unix software distributions under Linux. This HOWTO is
    22 available at <ulink
    23 url="http://www.tldp.org/HOWTO/Software-Building-HOWTO.html"/>.</para>
    24 </listitem>
    25 
    26 <listitem><para>The Linux Users' Guide</para>
    27 
    28 <para>This guide covers the usage of assorted Linux software and is
    29 available at
    30 <ulink url="http://espc22.murdoch.edu.au/~stewart/guide/guide.html"/>.</para></listitem>
    31 
    32 <listitem><para>The Essential Pre-Reading Hint</para>
    33 
    34 <para>This is an LFS Hint written specifically for new users of Linux. It is
    35 mostly a list of links to excellent sources of information on a wide range of
    36 topics. Any person attempting to install LFS, should at least have an
    37 understanding of many of the topics in this hint. It is available at
    38 
    39 <ulink url="&hints-root;essential_prereading.txt"/></para></listitem>
    40 
    41 </itemizedlist>
    42 -->
    43 
    4412</sect1>

  • prologue/typography.xml

    r96e5226 r90f6a46  
    1010<para>See testing</para>
    1111
    12 <!--
    13 <para>To make things easier to follow, there are a few typographical
    14 conventions used throughout the book. Following are some examples:</para>
    15 
    16 <screen><userinput>./configure -prefix=/usr</userinput></screen>
    17 
    18 <blockquote><para>This form of text is designed to be typed exactly
    19 as seen unless otherwise noted in the surrounding text. It is also used
    20 in the explanation sections to identify which of the commands is being
    21 referenced.</para></blockquote>
    22 
    23 <screen><computeroutput>install-info: unknown option `-dir-file=/mnt/lfs/usr/info/dir'</computeroutput></screen>
    24 
    25 <blockquote><para>This form of text (fixed width text) is showing screen
    26 output, probably as the result of commands issued, and is also used to
    27 show filenames, such as <filename>/etc/ld.so.conf</filename>.</para></blockquote>
    28 
    29 <para><emphasis>Emphasis</emphasis></para>
    30 
    31 <blockquote><para>This form of text is used for several purposes in the
    32 book, mainly to emphasize important points or items.</para></blockquote>
    33 
    34 <para><ulink url="&lfs-root;"/></para>
    35 
    36 <blockquote><para>This form of text is used for hyperlinks, both within the
    37 book and to external pages such as HOWTOs, download locations and
    38 websites.</para></blockquote>
    39 
    40 <screen><userinput>cat &gt; $LFS/etc/group &lt;&lt; "EOF"
    41 root:x:0:
    42 bin:x:1:
    43 ......
    44 EOF</userinput></screen>
    45 
    46 <blockquote><para>This type of section is used mainly when creating
    47 configuration files. The first command tells the system to create
    48 the file <filename>$LFS/etc/group</filename> from whatever is typed on the following lines until
    49 the sequence EOF is encountered. Therefore, this whole section is generally
    50 typed as seen.</para></blockquote>
    51 
    52 <para><replaceable>[REPLACED TEXT]</replaceable></para>
    53 
    54 <blockquote><para>This form of text is used to encapsulate text that is
    55 not to be typed as seen or copy and pasted.</para></blockquote>
    56 -->
    57 
    5812</sect1>
Note: See TracChangeset for help on using the changeset viewer.