Changeset b330f4a


Ignore:
Timestamp:
12/18/2005 12:25:25 PM (18 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.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:
7686ca6
Parents:
8e8f0039
Message:

Prologue indentation.

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

Location:
prologue
Files:
10 edited

Legend:

Unmodified
Added
Removed

  • prologue/audience.xml

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

  • prologue/bookinfo.xml

    r8e8f0039 rb330f4a  
    11<?xml version="1.0" encoding="ISO-8859-1"?>
    2 <!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
     2<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
     3  "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
    34  <!ENTITY % general-entities SYSTEM "../general.ent">
    45  %general-entities;
    56]>
     7
    68<bookinfo>
    7 <title>Linux From Scratch</title>
    8 <subtitle>Version &version;</subtitle>
     9  <title>Linux From Scratch</title>
     10  <subtitle>Version &version;</subtitle>
    911
    1012
    11 <authorgroup>
    12 <author><firstname>Gerard</firstname><surname>Beekmans</surname></author>
    13 </authorgroup>
     13  <authorgroup>
     14    <author>
     15      <firstname>Gerard</firstname>
     16      <surname>Beekmans</surname>
     17    </author>
     18  </authorgroup>
    1419
    1520
    16 <copyright id="copyright">
    17         <year>1999&ndash;2005</year>
    18         <holder>Gerard Beekmans</holder>
    19 </copyright>
     21  <copyright id="copyright">
     22    <year>1999&ndash;2005</year>
     23    <holder>Gerard Beekmans</holder>
     24  </copyright>
    2025
    21 <legalnotice>
    22 <para>Copyright (c) 1999&ndash;2005, Gerard Beekmans</para>
     26  <legalnotice>
     27    <para>Copyright (c) 1999&ndash;2005, Gerard Beekmans</para>
    2328
    24 <para>All rights reserved.</para>
     29    <para>All rights reserved.</para>
    2530
    26 <para>Redistribution and use in source and binary forms, with or without
    27 modification, are permitted provided that the following conditions are
    28 met:</para>
     31    <para>Redistribution and use in source and binary forms, with or without
     32    modification, are permitted provided that the following conditions are
     33    met:</para>
    2934
    30 <itemizedlist>
     35    <itemizedlist>
     36      <listitem>
     37        <para>Redistributions in any form must retain the above copyright
     38        notice, this list of conditions and the following disclaimer</para>
     39      </listitem>
     40      <listitem>
     41        <para>Neither the name of <quote>Linux From Scratch</quote> nor the
     42        names of its contributors may be used to endorse or promote products
     43        derived from  this material without specific prior written
     44        permission</para>
     45      </listitem>
     46      <listitem>
     47        <para>Any material derived from Linux From Scratch must contain
     48        a reference to the <quote>Linux From Scratch</quote> project</para>
     49      </listitem>
     50    </itemizedlist>
    3151
    32 <listitem><para>Redistributions in any form must retain the above copyright
    33 notice, this list of conditions and the following disclaimer</para></listitem>
     52    <para>THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
     53    <quote>AS IS</quote> AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING,
     54    BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
     55    FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR
     56    CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
     57    EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
     58    PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
     59    OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
     60    WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
     61    OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
     62    ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.</para>
    3463
    35 <listitem><para>Neither the name of <quote>Linux From Scratch</quote> nor the
    36 names of its contributors may be used to endorse or promote products derived
    37 from  this material without specific prior written permission</para></listitem>
    38 
    39 <listitem><para>Any material derived from Linux From Scratch must contain
    40 a reference to the <quote>Linux From Scratch</quote> project</para></listitem>
    41 
    42 </itemizedlist>
    43 
    44 <para>THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS <quote>AS
    45 IS</quote> AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
    46 TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
    47 PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR
    48 CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
    49 EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
    50 PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
    51 PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
    52 LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
    53 NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
    54 SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.</para>
    55 </legalnotice>
     64  </legalnotice>
    5665
    5766</bookinfo>
    58 

  • prologue/dedication.xml

    r8e8f0039 rb330f4a  
    11<?xml version="1.0" encoding="ISO-8859-1"?>
    2 <!DOCTYPE dedication PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
     2<!DOCTYPE dedication PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
     3  "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
    34  <!ENTITY % general-entities SYSTEM "../general.ent">
    45  %general-entities;
    56]>
     7
    68<dedication>
    7 <title>Dedication</title>
    8 <para>This book is dedicated</para>
     9  <title>Dedication</title>
     10  <para>This book is dedicated</para>
    911</dedication>
    10 

  • prologue/errata.xml

    r8e8f0039 rb330f4a  
    11<?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" [
     2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
     3  "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
    34  <!ENTITY % general-entities SYSTEM "../general.ent">
    45  %general-entities;
    56]>
     7
    68<sect1 id="pre-errata">
    7 <title>Errata</title>
    8 <?dbhtml filename="errata.html"?>
     9  <?dbhtml filename="errata.html"?>
    910
    10 <para>The software used to create an LFS system is constantly being updated and
    11 enhanced. Security warnings and bug fixes may become available after the LFS
    12 book has been released. To check whether the package versions or instructions in
    13 this release of LFS need any modifications to accommodate security
    14 vulnerabilities or other bug fixes, please visit <ulink url="&errata;"/> before
    15 proceeding with your build. You should note any changes shown and apply them to
    16 the relevant section of the book as you progress with building the LFS system.
    17 </para>
     11  <title>Errata</title>
     12
     13  <para>The software used to create an LFS system is constantly being updated
     14  and enhanced. Security warnings and bug fixes may become available after
     15  the LFS book has been released. To check whether the package versions or
     16  instructions in this release of LFS need any modifications to accommodate
     17  security vulnerabilities or other bug fixes, please visit <ulink
     18  url="&errata;"/> before proceeding with your build. You should note any
     19  changes shown and apply them to the relevant section of the book as you
     20  progress with building the LFS system.</para>
    1821
    1922</sect1>
    20 

  • prologue/foreword.xml

    r8e8f0039 rb330f4a  
    11<?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" [
     2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
     3  "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
    34  <!ENTITY % general-entities SYSTEM "../general.ent">
    45  %general-entities;
    56]>
     7
    68<sect1 id="pre-foreword">
    7 <title>Foreword</title>
    8 <?dbhtml filename="foreword.html"?>
     9  <?dbhtml filename="foreword.html"?>
    910
    10 <para>My adventures in Linux began in 1998 when I downloaded and
    11 installed my first distribution. After working with it for a while, I
    12 discovered issues I definitely would have liked to see improved upon.
    13 For example, I didn't like the arrangement of the bootscripts or the way
    14 programs were configured by default. I tried a number of alternative
    15 distributions to address these issues, yet each had its pros and cons.
    16 Finally, I realized that if I wanted full satisfaction from my Linux
    17 system, I would have to build my own from scratch.</para>
     11  <title>Foreword</title>
    1812
    19 <para>What does this mean? I resolved not to use pre-compiled packages
    20 of any kind, nor CD-ROMs or boot disks that would install basic
    21 utilities. I would use my current Linux system to develop my own
    22 customized system. This <quote>perfect</quote> Linux system would then
    23 have the strengths of various systems without their associated
    24 weaknesses. In the beginning, the idea was rather daunting, but I
    25 remained committed to the idea that a system could be built that would
    26 conform to my needs and desires rather than to a standard that just
    27 did not fit what I was looking for.</para>
     13  <para>My adventures in Linux began in 1998 when I downloaded and
     14  installed my first distribution. After working with it for a while, I
     15  discovered issues I definitely would have liked to see improved upon.
     16  For example, I didn't like the arrangement of the bootscripts or the way
     17  programs were configured by default. I tried a number of alternative
     18  distributions to address these issues, yet each had its pros and cons.
     19  Finally, I realized that if I wanted full satisfaction from my Linux
     20  system, I would have to build my own from scratch.</para>
    2821
    29 <para>After sorting through issues such as circular dependencies and
    30 compile-time errors, I created a custom-built Linux system that was
    31 fully operational and suitable to individual needs. This process also
    32 allowed me to create compact and streamlined Linux systems which are
    33 faster and take up less space than traditional operating systems. I
    34 called this system a Linux From Scratch system, or an LFS system for
    35 short.</para>
     22  <para>What does this mean? I resolved not to use pre-compiled packages
     23  of any kind, nor CD-ROMs or boot disks that would install basic
     24  utilities. I would use my current Linux system to develop my own
     25  customized system. This <quote>perfect</quote> Linux system would then
     26  have the strengths of various systems without their associated
     27  weaknesses. In the beginning, the idea was rather daunting, but I
     28  remained committed to the idea that a system could be built that would
     29  conform to my needs and desires rather than to a standard that just
     30  did not fit what I was looking for.</para>
    3631
    37 <para>As I shared my goals and experiences with other members of the
    38 Linux community, it became apparent that there was sustained interest
    39 in the ideas set forth in my Linux adventures. Such custom-built LFS
    40 systems serve not only to meet user specifications and requirements, but
    41 also serve as an ideal learning opportunity for programmers and system
    42 administrators to enhance their Linux skills. Out of this broadened
    43 interest, the Linux From Scratch Project was born.</para>
     32  <para>After sorting through issues such as circular dependencies and
     33  compile-time errors, I created a custom-built Linux system that was
     34  fully operational and suitable to individual needs. This process also
     35  allowed me to create compact and streamlined Linux systems which are
     36  faster and take up less space than traditional operating systems. I
     37  called this system a Linux From Scratch system, or an LFS system for
     38  short.</para>
    4439
    45 <para>This <emphasis>Linux From Scratch</emphasis> book provides
    46 readers with the background and instruction to design and build custom
    47 Linux systems. This book highlights the Linux from Scratch project and
    48 the benefits of using this system. Users can dictate all aspects of
    49 their system, including directory layout, script setup, and security.
    50 The resulting system will be compiled completely from the source code,
    51 and the user will be able to specify where, why, and how programs are
    52 installed. This book allows readers to fully customize Linux systems
    53 to their own needs and allows users more control over their
    54 system.</para>
     40  <para>As I shared my goals and experiences with other members of the
     41  Linux community, it became apparent that there was sustained interest
     42  in the ideas set forth in my Linux adventures. Such custom-built LFS
     43  systems serve not only to meet user specifications and requirements, but
     44  also serve as an ideal learning opportunity for programmers and system
     45  administrators to enhance their Linux skills. Out of this broadened
     46  interest, the Linux From Scratch Project was born.</para>
    5547
    56 <para>I hope you will have a great time working on your own LFS
    57 system, and enjoy the numerous benefits of having a system that is
    58 truly <emphasis>your own</emphasis>.</para>
     48  <para>This <emphasis>Linux From Scratch</emphasis> book provides
     49  readers with the background and instruction to design and build custom
     50  Linux systems. This book highlights the Linux from Scratch project and
     51  the benefits of using this system. Users can dictate all aspects of
     52  their system, including directory layout, script setup, and security.
     53  The resulting system will be compiled completely from the source code,
     54  and the user will be able to specify where, why, and how programs are
     55  installed. This book allows readers to fully customize Linux systems
     56  to their own needs and allows users more control over their
     57  system.</para>
    5958
    60 <para></para>
     59  <para>I hope you will have a great time working on your own LFS
     60  system, and enjoy the numerous benefits of having a system that is
     61  truly <emphasis>your own</emphasis>.</para>
    6162
    6263<literallayout>--
    … …  
    6566
    6667</sect1>
    67 

  • prologue/hostreqs.xml

    r8e8f0039 rb330f4a  
    11<?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" [
     2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
     3  "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
    34  <!ENTITY % general-entities SYSTEM "../general.ent">
    45  %general-entities;
    56]>
     7
    68<sect1 id="pre-hostreqs">
    7 <title>Host System Requirements</title>
    8 <?dbhtml filename="hostreqs.html"?>
     9  <?dbhtml filename="hostreqs.html"?>
    910
    10 <para>The host must be running at least a 2.6.2 kernel compiled with GCC-3.0 or
    11 higher. There are two main reasons for this requirement. First, the Native POSIX
    12 Threading Library (NPTL) test suite will segfault if the host's kernel has not
    13 been compiled with GCC-3.0 or a later version. Second, the 2.6.2 or later
    14 version of the kernel is required for the use of Udev. Udev creates devices
    15 dynamically by reading from the <systemitem
    16 class="filesystem">sysfs</systemitem> file system. However, support for this
    17 filesystem has only recently been implemented in most of the kernel drivers. We
    18 must be sure that all critical system devices get created properly.</para>
     11  <title>Host System Requirements</title>
    1912
    20 <para>In order to determine whether the host kernel meets the
    21 requirements outlined above, run the following command:</para>
     13  <para>The host must be running at least a 2.6.2 kernel compiled with GCC-3.0
     14  or higher. There are two main reasons for this requirement. First, the Native
     15  POSIX Threading Library (NPTL) test suite will segfault if the host's kernel
     16  has not been compiled with GCC-3.0 or a later version. Second, the 2.6.2 or
     17  later version of the kernel is required for the use of Udev. Udev creates
     18  devices dynamically by reading from the <systemitem
     19  class="filesystem">sysfs</systemitem> file system. However, support for this
     20  filesystem has only recently been implemented in most of the kernel drivers.
     21  We must be sure that all critical system devices get created properly.</para>
     22
     23  <para>In order to determine whether the host kernel meets the requirements
     24  outlined above, run the following command:</para>
    2225
    2326<screen role="nodump"><userinput>cat /proc/version</userinput></screen>
    2427
    25 <para>This will produce output similar to:</para>
     28  <para>This will produce output similar to:</para>
    2629
    2730<screen><computeroutput>Linux version 2.6.2 (user@host) (gcc version 3.4.0) #1
    2831    Tue Apr 20 21:22:18 GMT 2004</computeroutput></screen>
    2932
    30 <para>If the results of the above command do not state that the host kernel is
    31 either 2.6.2 (or later), or that it was not compiled using a GCC-3.0 (or later)
    32 compiler, one will need to be installed. There are two methods you can take to
    33 solve this. First, see if your Linux vendor provides a 2.6.2 (or later) kernel
    34 package. If so, you may wish to install it. If your vendor doesn't offer a 2.6.2
    35 (or later) kernel package, or you would prefer not to install it, then you can
    36 compile a 2.6 kernel yourself. Instructions for compiling the kernel and
    37 configuring the boot loader (assuming the host uses GRUB) are located in <xref
    38 linkend="chapter-bootable"/>. This second option can also be seen as a gauge
    39 of your current Linux skills. If this second requirement is too steep, then the
    40 LFS book will not likely be much use to you at this time.</para>
     33  <para>If the results of the above command do not state that the host kernel
     34  is either 2.6.2 (or later), or that it was not compiled using a GCC-3.0 (or
     35  later) compiler, one will need to be installed. There are two methods you
     36  can take to solve this. First, see if your Linux vendor provides a 2.6.2 (or
     37  later) kernel package. If so, you may wish to install it. If your vendor
     38  doesn't offer a 2.6.2 (or later) kernel package, or you would prefer not to
     39  install it, then you can compile a 2.6 kernel yourself. Instructions for
     40  compiling the kernel and configuring the boot loader (assuming the host
     41  uses GRUB) are located in <xref linkend="chapter-bootable"/>. This second
     42  option can also be seen as a gauge of your current Linux skills. If this
     43  second requirement is too steep, then the LFS book will not likely be much
     44  use to you at this time.</para>
    4145
    4246</sect1>
    43 

  • prologue/organization.xml

    r8e8f0039 rb330f4a  
    11<?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" [
     2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
     3  "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
    34  <!ENTITY % general-entities SYSTEM "../general.ent">
    45  %general-entities;
    56]>
     7
    68<sect1 id="pre-organization">
    7 <title>Structure</title>
    8 <?dbhtml filename="organization.html"?>
     9  <?dbhtml filename="organization.html"?>
    910
    10 <para>This book is divided into the following parts.</para>
     11  <title>Structure</title>
    1112
    12 <sect2>
    13 <title>Part I - Introduction</title>
     13  <para>This book is divided into the following parts.</para>
    1414
    15 <para>Part I explains a few important notes on how to proceed with the
    16 LFS installation.  This section also provides meta-information about
    17 the book.</para>
    18 </sect2>
     15  <sect2>
     16    <title>Part I - Introduction</title>
    1917
    20 <sect2>
    21 <title>Part II - Preparing for the Build</title>
     18    <para>Part I explains a few important notes on how to proceed with the
     19    LFS installation.  This section also provides meta-information about
     20    the book.</para>
     21  </sect2>
    2222
    23 <para>Part II describes how to prepare for the building process&mdash;making
    24 a partition, downloading the packages, and compiling temporary
    25 tools.</para>
    26 </sect2>
     23  <sect2>
     24    <title>Part II - Preparing for the Build</title>
    2725
    28 <sect2>
    29 <title>Part III - Building the LFS System</title>
     26    <para>Part II describes how to prepare for the building process&mdash;making
     27    a partition, downloading the packages, and compiling temporary
     28    tools.</para>
     29  </sect2>
    3030
    31 <para>Part III guides the reader through the building of the LFS
    32 system&mdash;compiling and installing all the packages one by one,
    33 setting up the boot scripts, and installing the kernel. The resulting
    34 Linux system is the foundation on which other software can be built to
    35 expand the system as desired. At the end of this book, there is an
    36 easy to use reference listing all of the programs, libraries, and
    37 important files that have been installed.</para>
    38 </sect2>
     31  <sect2>
     32    <title>Part III - Building the LFS System</title>
     33
     34    <para>Part III guides the reader through the building of the LFS
     35    system&mdash;compiling and installing all the packages one by one,
     36    setting up the boot scripts, and installing the kernel. The resulting
     37    Linux system is the foundation on which other software can be built to
     38    expand the system as desired. At the end of this book, there is an
     39    easy to use reference listing all of the programs, libraries, and
     40    important files that have been installed.</para>
     41  </sect2>
    3942
    4043</sect1>

  • prologue/preface.xml

    r8e8f0039 rb330f4a  
    11<?xml version="1.0" encoding="ISO-8859-1"?>
    2 <!DOCTYPE preface PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
     2<!DOCTYPE preface PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
     3  "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
    34  <!ENTITY % general-entities SYSTEM "../general.ent">
    45  %general-entities;
    56]>
     7
    68<preface id="preface">
    7 <?dbhtml dir="prologue"?>
    8 <title>Preface</title>
    9 <?dbhtml filename="preface.html"?>
     9  <?dbhtml dir="prologue"?>
     10  <?dbhtml filename="preface.html"?>
    1011
    11 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="foreword.xml"/>
    12 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="audience.xml"/>
    13 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="prerequisites.xml"/>
    14 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="hostreqs.xml"/>
    15 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="typography.xml"/>
    16 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="organization.xml"/>
    17 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="errata.xml"/>
     12  <title>Preface</title>
     13
     14  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="foreword.xml"/>
     15  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="audience.xml"/>
     16  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="prerequisites.xml"/>
     17  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="hostreqs.xml"/>
     18  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="typography.xml"/>
     19  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="organization.xml"/>
     20  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="errata.xml"/>
    1821
    1922</preface>

  • prologue/prerequisites.xml

    r8e8f0039 rb330f4a  
    11<?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" [
     2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
     3  "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
    34  <!ENTITY % general-entities SYSTEM "../general.ent">
    45  %general-entities;
    56]>
     7
    68<sect1 id="pre-prerequisites">
    7 <title>Prerequisites</title>
    8 <?dbhtml filename="prerequisites.html"?>
     9  <?dbhtml filename="prerequisites.html"?>
    910
    10 <para>Building an LFS system is not a simple task. It requires a certain level
    11 of existing knowledge of Unix system administration in order to resolve
    12 problems, and correctly execute the commands listed.  In particular, as an
    13 absolute minimum, the reader should already have the ability to use the command
    14 line (shell) to copy or move files and directories, list directory and file
    15 contents, and change the current directory.  It is also expected that the reader
    16 has a reasonable knowledge of using and installing Linux software.</para>
     11  <title>Prerequisites</title>
    1712
    18 <para>Because the LFS book assumes <emphasis>at least</emphasis> this basic
    19 level of skill, the various LFS support forums are unlikely to be able to
    20 provide you with much assistance; you will find that your questions regarding
    21 such basic knowledge will likely go unanswered, or you will simply be referred
    22 to the LFS essential pre-reading list.</para>
     13  <para>Building an LFS system is not a simple task. It requires a certain
     14  level of existing knowledge of Unix system administration in order to resolve
     15  problems, and correctly execute the commands listed. In particular, as an
     16  absolute minimum, the reader should already have the ability to use the
     17  command line (shell) to copy or move files and directories, list directory
     18  and file contents, and change the current directory. It is also expected that
     19  the reader has a reasonable knowledge of using and installing Linux
     20  software.</para>
    2321
    24 <para>Before building an LFS system, we recommend reading the following HOWTOs:
    25 </para>
     22  <para>Because the LFS book assumes <emphasis>at least</emphasis> this basic
     23  level of skill, the various LFS support forums are unlikely to be able to
     24  provide you with much assistance; you will find that your questions regarding
     25  such basic knowledge will likely go unanswered, or you will simply be referred
     26  to the LFS essential pre-reading list.</para>
    2627
    27 <itemizedlist>
    28 <listitem><para>Software-Building-HOWTO
    29 <ulink url="http://www.tldp.org/HOWTO/Software-Building-HOWTO.html"/></para>
     28  <para>Before building an LFS system, we recommend reading the following
     29  HOWTOs:</para>
    3030
    31 <para>This is a comprehensive guide to building and installing
    32 <quote>generic</quote> Unix software distributions under Linux.</para></listitem>
     31  <itemizedlist>
     32    <listitem>
     33      <para>Software-Building-HOWTO
     34      <ulink url="http://www.tldp.org/HOWTO/Software-Building-HOWTO.html"/></para>
    3335
    34 <listitem><para>The Linux Users' Guide
    35 <ulink url="http://www.linuxhq.com/guides/LUG/guide.html"/></para>
     36      <para>This is a comprehensive guide to building and installing
     37      <quote>generic</quote> Unix software distributions under Linux.</para>
     38    </listitem>
    3639
    37 <para>This guide covers the usage of assorted Linux software.</para></listitem>
     40    <listitem>
     41      <para>The Linux Users' Guide
     42      <ulink url="http://www.linuxhq.com/guides/LUG/guide.html"/></para>
    3843
    39 <listitem><para>The Essential Pre-Reading Hint
    40 <ulink url="&hints-root;essential_prereading.txt"/></para>
     44      <para>This guide covers the usage of assorted Linux software.</para>
     45    </listitem>
    4146
    42 <para>This is an LFS Hint written specifically for users new to Linux.
    43 It includes a list of links to excellent sources of information on a
    44 wide range of topics. Anyone attempting to install LFS should have an
    45 understanding of many of the topics in this hint.</para></listitem>
     47    <listitem>
     48      <para>The Essential Pre-Reading Hint
     49      <ulink url="&hints-root;essential_prereading.txt"/></para>
    4650
    47 </itemizedlist>
     51      <para>This is an LFS Hint written specifically for users new to Linux.
     52      It includes a list of links to excellent sources of information on a
     53      wide range of topics. Anyone attempting to install LFS should have an
     54      understanding of many of the topics in this hint.</para>
     55    </listitem>
     56
     57  </itemizedlist>
    4858
    4959</sect1>
    50 

  • prologue/typography.xml

    r8e8f0039 rb330f4a  
    11<?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" [
     2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
     3  "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
    34  <!ENTITY % general-entities SYSTEM "../general.ent">
    45  %general-entities;
    56]>
     7
    68<sect1 id="pre-typography">
    7 <title>Typography</title>
    8 <?dbhtml filename="typography.html"?>
     9  <?dbhtml filename="typography.html"?>
    910
    10 <para>To make things easier to follow, there are a few typographical
    11 conventions used throughout this book. This section contains some
    12 examples of the typographical format found throughout Linux From
    13 Scratch.</para>
     11  <title>Typography</title>
     12
     13  <para>To make things easier to follow, there are a few typographical
     14  conventions used throughout this book. This section contains some
     15  examples of the typographical format found throughout Linux From
     16  Scratch.</para>
    1417
    1518<screen role="nodump"><userinput>./configure --prefix=/usr</userinput></screen>
    1619
    17 <para>This form of text is designed to be typed exactly as seen unless
    18 otherwise noted in the surrounding text. It is also used in the
    19 explanation sections to identify which of the commands is being
    20 referenced.</para>
     20  <para>This form of text is designed to be typed exactly as seen unless
     21  otherwise noted in the surrounding text. It is also used in the explanation
     22  sections to identify which of the commands is being referenced.</para>
    2123
    2224<screen><computeroutput>install-info: unknown option '--dir-file=/mnt/lfs/usr/info/dir'</computeroutput></screen>
    2325
    24 <para>This form of text (fixed-width text) shows screen output,
    25 probably as the result of commands issued.  This format is also used
    26 to show filenames, such as
    27 <filename>/etc/ld.so.conf</filename>.</para>
     26  <para>This form of text (fixed-width text) shows screen output, probably as
     27  the result of commands issued.  This format is also used to show filenames,
     28  such as <filename>/etc/ld.so.conf</filename>.</para>
    2829
    29 <para><emphasis>Emphasis</emphasis></para>
     30  <para><emphasis>Emphasis</emphasis></para>
    3031
    31 <para>This form of text is used for several purposes in the book. Its main
    32 purpose is to emphasize important points or items.</para>
     32  <para>This form of text is used for several purposes in the book. Its main
     33  purpose is to emphasize important points or items.</para>
    3334
    34 <para><ulink url="&lfs-root;"/></para>
     35  <para><ulink url="&lfs-root;"/></para>
    3536
    36 <para>This format is used for hyperlinks both within the LFS
    37 community and to external pages.  It includes HOWTOs, download locations,
    38 and websites.</para>
     37  <para>This format is used for hyperlinks both within the LFS community and to
     38  external pages. It includes HOWTOs, download locations, and websites.</para>
    3939
    4040<screen role="nodump"><userinput>cat &gt; $LFS/etc/group &lt;&lt; "EOF"
    … …  
    4444EOF</userinput></screen>
    4545
    46 <para>This format is used when creating configuration files. The first
    47 command tells the system to create the file
    48 <filename>$LFS/etc/group</filename> from whatever is typed on the
    49 following lines until the sequence end of file (EOF) is encountered.
    50 Therefore, this entire section is generally typed as seen.</para>
     46  <para>This format is used when creating configuration files. The first command
     47  tells the system to create the file <filename>$LFS/etc/group</filename> from
     48  whatever is typed on the following lines until the sequence end of file (EOF)
     49  is encountered. Therefore, this entire section is generally typed as
     50  seen.</para>
    5151
    52 <para><replaceable>[REPLACED TEXT]</replaceable></para>
     52  <para><replaceable>[REPLACED TEXT]</replaceable></para>
    5353
    54 <para>This format is used to encapsulate text that is not to be typed
    55 as seen or copied-and-pasted.</para>
     54  <para>This format is used to encapsulate text that is not to be typed
     55  as seen or copied-and-pasted.</para>
    5656
    57 <para><filename>passwd(5)</filename></para>
     57  <para><filename>passwd(5)</filename></para>
    5858
    59 <para>This format is used to refer to a specific manual page (hereinafter
    60 referred to simply as a <quote>man</quote> page). The number inside parentheses
    61 indicates a specific section inside of <command>man</command>. For example,
    62 <command>passwd</command> has two man pages. Per LFS installation instructions,
    63 those two man pages will be located at
    64 <filename>/usr/share/man/man1/passwd.1</filename> and
    65 <filename>/usr/share/man/man5/passwd.5</filename>. Both man pages have different
    66 information in them. When the book uses <filename>passwd(5)</filename> it is
    67 specifically referring to <filename>/usr/share/man/man5/passwd.5</filename>.
    68 <command>man passwd</command> will print the first man page it finds that
    69 matches <quote>passwd</quote>, which will be
    70 <filename>/usr/share/man/man1/passwd.1</filename>. For this example, you will
    71 need to run <command>man 5 passwd</command> in order to read the specific page
    72 being referred to. It should be noted that most man pages do not have duplicate
    73 page names in different sections. Therefore, <command>man <replaceable>[program
    74 name]</replaceable></command> is generally sufficient.</para>
     59  <para>This format is used to refer to a specific manual page (hereinafter
     60  referred to simply as a <quote>man</quote> page). The number inside parentheses
     61  indicates a specific section inside of <command>man</command>. For example,
     62  <command>passwd</command> has two man pages. Per LFS installation instructions,
     63  those two man pages will be located at
     64  <filename>/usr/share/man/man1/passwd.1</filename> and
     65  <filename>/usr/share/man/man5/passwd.5</filename>. Both man pages have different
     66  information in them. When the book uses <filename>passwd(5)</filename> it is
     67  specifically referring to <filename>/usr/share/man/man5/passwd.5</filename>.
     68  <command>man passwd</command> will print the first man page it finds that
     69  matches <quote>passwd</quote>, which will be
     70  <filename>/usr/share/man/man1/passwd.1</filename>. For this example, you will
     71  need to run <command>man 5 passwd</command> in order to read the specific page
     72  being referred to. It should be noted that most man pages do not have duplicate
     73  page names in different sections. Therefore, <command>man <replaceable>[program
     74  name]</replaceable></command> is generally sufficient.</para>
    7575
    7676</sect1>
Note: See TracChangeset for help on using the changeset viewer.