Changeset 4afc2603


Ignore:
Timestamp:
12/29/2005 01:24:51 AM (16 years ago)
Author:
Randy McMurchy <randy@…>
Branches:
10.0, 10.1, 11.0, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, krejzi/svn, lazarus, nosym, perl-modules, qt5new, systemd-11177, systemd-13485, trunk, xry111/git-date, xry111/git-date-for-trunk, xry111/git-date-test
Children:
5254d12
Parents:
17be8c3
Message:

Changes to the Introduction section; standardized the file structure layout, standardized the id tags (except bootscripts) and some minor textual modifications

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@5496 af4574ff-66df-0310-9fd7-8a98e5e911e0

Files:
2 added
18 edited

Legend:

Unmodified
Added
Removed
  • book/preface.xml

    r17be8c3 r4afc2603  
    106106
    107107      <para>Changes and upgrades to the individual packages are detailed in the
    108       <xref linkend='intro-welcome-changelog'/>.  There you will see literally hundreds of
     108      <xref linkend='changelog'/>.  There you will see literally hundreds of
    109109      changes made since the last edition.  In this change log, one name that you
    110110      will see over and over is Randy McMurchy.  Without his efforts this
     
    144144      extending a basic Linux From Scratch system.    The instructions in this
    145145      version of BLFS are based on the LFS 6.1 Book.  As usual, the list of
    146       packages that have been upgraded or added are in the <xref
    147       linkend='intro-welcome-changelog'/>.</para>
     146      packages that have been upgraded or added are in the
     147      <xref linkend='changelog'/>.</para>
    148148
    149149      <para>One major accomplishment in this
  • introduction/important/beyond.xml

    r17be8c3 r4afc2603  
    66]>
    77
    8 <sect1 id="intro-important-beyond">
     8<sect1 id="beyond" xreflabel="Going Beyond BLFS">
    99  <?dbhtml filename="beyond.html"?>
    1010
     
    4242      <para>Add <filename class='directory'>$PREFIX/lib</filename>
    4343      to <filename>/etc/ld.so.conf</filename> or expand
    44       <envar>LD_LIBRARY_PATH</envar> to include it. Before using the latter option,
    45       check out <ulink url="http://www.visi.com/~barr/ldpath.html"/>. If you
    46       modify <filename>/etc/ld.so.conf</filename>, remember to update
    47       <filename>/etc/ld.so.cache</filename> by executing <command>ldconfig</command>
    48       as the <systemitem class="username">root</systemitem> user.</para>
     44      <envar>LD_LIBRARY_PATH</envar> to include it. Before using the latter
     45      option, check out <ulink url="http://www.visi.com/~barr/ldpath.html"/>.
     46      If you modify <filename>/etc/ld.so.conf</filename>, remember to update
     47      <filename>/etc/ld.so.cache</filename> by executing
     48      <command>ldconfig</command> as the
     49      <systemitem class="username">root</systemitem> user.</para>
    4950    </listitem>
    5051    <listitem>
    5152      <para>Add <filename class='directory'>$PREFIX/man</filename>
    52       to <filename>/etc/man.conf</filename> or expand <envar>MANPATH</envar>.</para>
     53      to <filename>/etc/man.conf</filename> or expand
     54      <envar>MANPATH</envar>.</para>
    5355    </listitem>
    5456    <listitem>
     
    5759    </listitem>
    5860    <listitem>
    59       <para>Add <filename
    60       class='directory'>$PREFIX/lib/pkgconfig</filename> to
    61       <envar>PKG_CONFIG_PATH</envar>.</para>
     61      <para>Add <filename class='directory'>$PREFIX/lib/pkgconfig</filename>
     62      to <envar>PKG_CONFIG_PATH</envar>. Some packages are now installing
     63      <filename class='extension'>.pc</filename> files in
     64      <filename class='directory'>$PREFIX/share/pkgconfig</filename>, so you may
     65      have to include this directory also.</para>
    6266    </listitem>
    6367    <listitem>
     
    6973
    7074  <para>If you are in search of a package that is not in the book, the following
    71   are different ways you can search for the concerned package.</para>
     75  are different ways you can search for the desired package.</para>
    7276
    7377  <itemizedlist>
     
    7579      <para>If you know the name of the package, then search FreshMeat for
    7680      it at <ulink url="http://freshmeat.net/"/>. Also search Google at
    77       <ulink url="http://google.com/"/>. Sometimes a search for the rpm at
    78       <ulink url="http://rpmfind.net/"/> or the deb at
    79       <ulink url="http://www.debian.org/distrib/packages#search_packages"/> can also
    80       lead to a link to the package.</para>
     81      <ulink url="http://google.com/"/>. Sometimes a search for the
     82      <filename class='extension'>rpm</filename> at
     83      <ulink url="http://rpmfind.net/"/> or the
     84      <filename class='extension'>deb</filename> at
     85      <ulink url="http://www.debian.org/distrib/packages#search_packages"/> can
     86      also lead to a link to the package.</para>
    8187    </listitem>
    8288    <listitem>
    8389      <para>If you know the name of the executable, but not the package
    84       that the executable belongs to, first try a google search with the name of the
    85       executable. If the results are overwhelming, try searching for the given
    86       executable in the Debian repository at
    87       <ulink url="http://www.debian.org/distrib/packages#search_contents"/>.</para>
     90      that the executable belongs to, first try a Google search with the name
     91      of the executable. If the results are overwhelming, try searching for the
     92      given executable in the Debian repository at <ulink
     93      url="http://www.debian.org/distrib/packages#search_contents"/>.</para>
    8894    </listitem>
    8995  </itemizedlist>
     
    101107      <para>Most of the packages contain documentation on compiling and
    102108      installing the package. Some of the documents are excellent, some not so
    103       excellent. Check out the homepage of the package for any additional and updated
    104       hints for compiling and configuring the package.</para>
     109      excellent. Check out the homepage of the package for any additional and
     110      updated hints for compiling and configuring the package.</para>
    105111    </listitem>
    106112    <listitem>
    107113      <para>If you are having a problem compiling the package, try
    108       searching the lfs archives at <ulink url="http://search.linuxfromscratch.org/"/>
    109       for the error or if that fails try searching Google. If everything else fails,
    110       try the blfs-support mailing-list/news-group.</para>
     114      searching the LFS archives at
     115      <ulink url="http://search.linuxfromscratch.org/"/> for the error or if
     116      that fails, try searching Google. If everything else fails,
     117      try the blfs-support mailing-list.</para>
    111118    </listitem>
    112119  </itemizedlist>
    113120
    114121  <tip>
    115     <para>If you have found a package that is only available in .deb or .rpm
     122    <para>If you have found a package that is only available in
     123    <filename class='extension'>.deb</filename> or
     124    <filename class='extension'>.rpm</filename>
    116125    format, there are two small scripts, <command>rpm2targz</command> and
    117126    <command>deb2targz</command> that are available at
  • introduction/important/patches.xml

    r17be8c3 r4afc2603  
    66]>
    77
    8 <sect1 id="intro-important-patches">
     8<sect1 id="patches">
    99  <?dbhtml filename="patches.html"?>
    1010
  • introduction/important/pkgmgt.xml

    r17be8c3 r4afc2603  
    66]>
    77
    8 <sect1 id="intro-important-pkgmgt">
     8<sect1 id="pkgmgt">
    99  <?dbhtml filename="pkgmgt.html"?>
    1010
     
    4343  <para>There are some hints written on the topic of package management. Visit
    4444  the <ulink url="&hints-root;">Hints subproject</ulink>
    45   to find if one of them fits your need.</para>
     45  and see if one of them fits your need.</para>
    4646
    4747  <sect2>
     
    8686        <para>If you are upgrading a running system, be on the lookout for packages
    8787        that use <command>cp</command> instead of <command>install</command>
    88         to install files. The latter command is usually safer if the executable or library
    89         is already loaded in memory.</para>
     88        to install files. The latter command is usually safer if the executable
     89        or library is already loaded in memory.</para>
    9090      </listitem>
    9191    </itemizedlist>
     
    114114      <title>Install in Separate Directories</title>
    115115
    116       <para>This is a simplistic package management that does not need any extra package
    117       to manage the installations. Each package is installed in a separate directory.
    118       For example, package foo-1.1 is installed in
     116      <para>This is a simplistic package management that does not need any
     117      extra package to manage the installations. Each package is installed in a
     118      separate directory. For example, package foo-1.1 is installed in
    119119      <filename class='directory'>/usr/pkg/foo-1.1</filename>
    120120      and a symlink is made from <filename>/usr/pkg/foo</filename> to
     
    125125
    126126      <para>The environment variables such as those mentioned in
    127       <xref linkend="intro-important-beyond"/> need to be expanded to
     127      <quote><xref linkend="beyond"/></quote> need to be expanded to
    128128      include <filename>/usr/pkg/foo</filename>. For more than a few packages,
    129129      this scheme becomes unmanageable.</para>
  • introduction/important/position.xml

    r17be8c3 r4afc2603  
    66]>
    77
    8 <sect1 id="intro-important-position">
     8<sect1 id="position">
    99  <?dbhtml filename="position.html"?>
    1010
     
    2222  LFS based system.</para>
    2323
    24   <para>In traditional Unix systems, <filename>/usr</filename> usually
    25   contains files that come with the system distribution, and the <filename>
    26   /usr/local</filename> tree is free for the local administrator to manage.
    27   The only really hard and fast rule is that Unix distributions should not
    28   touch <filename>/usr/local</filename>, except perhaps to create the basic
    29   directories within it.</para>
     24  <para>In traditional Unix systems,
     25  <filename class='directory'>/usr</filename> usually contains files that come
     26  with the system distribution, and the
     27  <filename class='directory'>/usr/local</filename> tree is free for the local
     28  administrator to manage. The only really hard and fast rule is that Unix
     29  distributions should not touch
     30  <filename class='directory'>/usr/local</filename>, except perhaps to create
     31  the basic directories within it.</para>
    3032
    31   <para>With Linux distributions, like Red Hat, Debian etc. a possible rule is
    32   that <filename>/usr</filename> is managed by the distribution's
    33   package system and <filename>/usr/local</filename> is not.  This way the
     33  <para>With Linux distributions like Red Hat, Debian, etc., a possible rule is
     34  that <filename class='directory'>/usr</filename> is managed by the
     35  distribution's package system and
     36  <filename class='directory'>/usr/local</filename> is not. This way the
    3437  package manager's database knows about every file within
    35   <filename>/usr</filename>.</para>
     38  <filename class='directory'>/usr</filename>.</para>
    3639
    3740  <para>LFS users build their own system and so deciding where
    3841  the system ends and local files begin is not straightforward.  So the choice
    39   should be made in order to make things easier to administer.  There are several
    40   reasons for dividing files between <filename>/usr</filename> and
    41   <filename>/usr/local</filename>.</para>
     42  should be made in order to make things easier to administer.  There are
     43  several reasons for dividing files between
     44  <filename class='directory'>/usr</filename> and
     45  <filename class='directory'>/usr/local</filename>.</para>
    4246
    4347  <itemizedlist>
    4448    <listitem>
    45       <para>On a network of several machines all running LFS,
    46       or mixed LFS and other Linux distributions,
    47       <filename>/usr/local</filename> could be used to hold packages
    48       that are common between all the computers in the network.  It can be
    49       NFS mounted or mirrored from a single server.  Here local
    50       indicates local to the site.</para>
     49      <para>On a network of several machines all running LFS, or mixed LFS and
     50      other Linux distributions,
     51      <filename class='directory'>/usr/local</filename> could be used to hold
     52      packages that are common between all the computers in the network. It can
     53      be NFS mounted or mirrored from a single server. Here local indicates
     54      local to the site.</para>
    5155    </listitem>
    5256    <listitem>
    5357      <para>On a network of several computers all running an identical
    54       LFS system <filename>/usr/local</filename> could hold
    55       packages that are different between the machines.  In this case local refers
    56       to the individual computers.</para>
     58      LFS system, <filename class='directory'>/usr/local</filename> could hold
     59      packages that are different between the machines. In this case local
     60      refers to the individual computers.</para>
    5761    </listitem>
    5862    <listitem>
    59       <para>Even on a single computer <filename>/usr/local</filename> can
    60       be useful if you have several distributions installed simultaneously, and want
     63      <para>Even on a single computer,
     64      <filename class='directory'>/usr/local</filename> can be useful if you
     65      have several distributions installed simultaneously, and want
    6166      a place to put packages that will be the same on all of them.</para>
    6267    </listitem>
    6368    <listitem>
    6469      <para>Or you might regularly rebuild your LFS, but
    65       want a place to put files that you don't want to rebuild each time.  This way
    66       you can wipe the LFS file system and start from a clean
     70      want a place to put files that you don't want to rebuild each time.  This
     71      way you can wipe the LFS file system and start from a clean
    6772      partition every time without losing everything.</para>
    6873    </listitem>
    6974  </itemizedlist>
    7075
    71   <para>Some people ask why not use your own directory tree, e.g., <filename>
    72   /usr/site</filename>, rather than <filename>/usr/local</filename>?</para>
     76  <para>Some people ask why not use your own directory tree, e.g.,
     77  <filename class='directory'>/usr/site</filename>, rather than
     78  <filename class='directory'>/usr/local</filename>?</para>
    7379
    7480  <para>There is nothing stopping you, many sites do make their own trees,
    7581  however it makes installing new software more difficult.  Automatic installers
    76   often look for dependencies in <filename>/usr</filename> and
    77   <filename>/usr/local</filename>, and if the file it is looking
    78   for is in <filename>/usr/site</filename> instead, the installer will
    79   probably fail unless you specifically tell it where to look.</para>
     82  often look for dependencies in
     83  <filename class='directory'>/usr</filename> and
     84  <filename class='directory'>/usr/local</filename>, and if the file it is
     85  looking for is in <filename class='directory'>/usr/site</filename> instead,
     86  the installer will probably fail unless you specifically tell it where to
     87  look.</para>
    8088
    8189  <para><emphasis>What is the BLFS position on this?</emphasis></para>
    8290
    8391  <para>All of the BLFS instructions install programs in
    84   <filename>/usr</filename> with optional instructions to install into
    85   <filename>/opt</filename> for some specific packages.</para>
     92  <filename class='directory'>/usr</filename> with optional instructions to
     93  install into <filename class='directory'>/opt</filename> for some specific
     94  packages.</para>
    8695
    8796</sect1>
  • introduction/important/unpacking.xml

    r17be8c3 r4afc2603  
    66]>
    77
    8 <sect1 id="intro-important-unpacking">
     8<sect1 id="unpacking">
    99  <?dbhtml filename="unpacking.html"?>
    1010
     
    1616  <title>Notes on Building Software</title>
    1717
    18   <para>Those people who have built an LFS system will be aware
     18  <para>Those people who have built an LFS system may be aware
    1919  of the general principles of downloading and unpacking software.  We will
    2020  however repeat some of that information here for those new to building
     
    3434  <para>We can not emphasize strongly enough that you should start from a
    3535  <emphasis>clean source tree</emphasis> each time. This means that if
    36   you have had an error, it's usually best to delete the source tree and
     36  you have had an error during configuration or compilation, it's usually
     37  best to delete the source tree and
    3738  re-unpack it <emphasis>before</emphasis> trying again. This obviously
    3839  doesn't apply if you're an advanced user used to hacking
     
    143144    <itemizedlist>
    144145      <listitem>
    145         <para><emphasis>Required</emphasis> means
    146             that the target package cannot be correctly built without
    147             the dependency having first been installed.</para>
     146        <para><emphasis>Required</emphasis> means that the target package
     147        cannot be correctly built without the dependency having first been
     148        installed.</para>
    148149      </listitem>
    149150      <listitem>
    150         <para><emphasis>Recommended</emphasis> means that BLFS strongly suggests this package is
    151            installed first for a clean and trouble-free build, that won't have
    152            issues either during the build process, or at run-time.</para>
     151        <para><emphasis>Recommended</emphasis> means that BLFS strongly
     152        suggests this package is installed first for a clean and trouble-free
     153        build, that won't have issues either during the build process, or at
     154        run-time.</para>
    153155      </listitem>
    154156      <listitem>
    155         <para><emphasis>Optional</emphasis> means that this package might be installed for added
    156            functionality.  Often BLFS will qualify the dependency to explain the
    157           added functionality that will result.</para>
     157        <para><emphasis>Optional</emphasis> means that this package might be
     158        installed for added functionality. Often BLFS will describe the
     159        dependency to explain the added functionality that will result.</para>
    158160      </listitem>
    159161    </itemizedlist>
  • introduction/introduction.xml

    r17be8c3 r4afc2603  
    1111  <title>Introduction</title>
    1212
    13   <chapter id="intro-welcome">
    14     <?dbhtml filename="welcome.html"?>
    15 
    16     <title>Welcome to BLFS</title>
    17 
    18     <para>The Beyond Linux From Scratch book is designed to carry on from
    19     where the LFS book leaves off.  But unlike the LFS book, it isn't designed to
    20     be followed straight through.  Reading the <xref
    21     linkend="intro-welcome-whichsections"/> part of this chapter should help
    22     guide you through the book.</para>
    23 
    24     <para>Please read most of this part of the book carefully as it explains
    25     quite a few of the conventions we use throughout the book.</para>
    26 
    27 
    28     <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="welcome/acknowledgments.xml"/>
    29     <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="welcome/credits.xml"/>
    30     <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="welcome/which.xml"/>
    31     <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="welcome/conventions.xml"/>
    32     <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="welcome/version.xml"/>
    33     <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="welcome/mirrors.xml"/>
    34     <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="welcome/packages.xml"/>
    35     <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="welcome/changelog.xml"/>
    36     <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="welcome/maillists.xml"/>
    37  <!--   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="welcome/newsserver.xml"/> -->
    38     <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="welcome/askhelp.xml"/>
    39     <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="welcome/contact.xml"/>
    40 
    41   </chapter>
    42 
    43   <chapter id="intro-important">
    44     <?dbhtml filename="important.html"?>
    45 
    46     <title>Important Information</title>
    47 
    48     <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="important/pkgmgt.xml"/>
    49     <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="important/unpacking.xml"/>
    50     <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="important/position.xml"/>
    51     <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="important/patches.xml"/>
    52     <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="important/bootscripts.xml"/>
    53     <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="important/beyond.xml"/>
    54 
    55   </chapter>
     13  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="welcome/welcome.xml"/>
     14  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="important/important.xml"/>
    5615
    5716</part>
  • introduction/welcome/acknowledgments.xml

    r17be8c3 r4afc2603  
    66]>
    77
    8 <sect1 id="intro-welcome-acknowledgments">
     8<sect1 id="acknowledgments">
    99  <?dbhtml filename="acknowledgments.html"?>
    1010
     
    7171
    7272</sect1>
    73 
  • introduction/welcome/askhelp.xml

    r17be8c3 r4afc2603  
    66]>
    77
    8 <sect1 id="intro-welcome-askhelp">
     8<sect1 id="askhelp">
    99  <?dbhtml filename="askhelp.html"?>
    1010
     
    2020  you will find that most of the people on Internet Relay Chat (IRC) and on the
    2121  mailing lists are willing to help you. An overview of the LFS mailing
    22   lists can be found in <xref linkend="intro-welcome-maillists"/>. To assist us
     22  lists can be found in <xref linkend="maillists"/>. To assist us
    2323  in diagnosing and solving your problem, include as much relevant information
    2424  as possible in your request for help.</para>
     
    3636        been loaded?  You should use <command>lsmod</command> as the
    3737        <systemitem class='username'>root</systemitem> user to see if it's
    38         loaded. Check the <filename>syslog.log</filename> or run
     38        loaded. Check the <filename>syslog.log</filename> file or run
    3939        <command>modprobe <replaceable>[driver]</replaceable></command> to
    4040        review any error message. If it loads properly, you may need to add
     
    5757        PATH=$PATH:/opt/kde/bin). In most cases, the package instructions will
    5858        walk you through the changes, but some will not. The section called
    59         <quote><ulink url="beyond.html">Going Beyond BLFS</ulink></quote> is
     59        <quote><xref linkend="beyond"/></quote> is
    6060        available to help you check.</para>
    6161      </listitem>
  • introduction/welcome/changelog.xml

    r17be8c3 r4afc2603  
    66]>
    77
    8 <sect1 id="intro-welcome-changelog" xreflabel='Change Log'>
     8<sect1 id="changelog" xreflabel='Change Log'>
    99  <?dbhtml filename="changelog.html"?>
    1010
     
    1818  <para>Please note that the Change Log only lists which editor was
    1919  responsible for putting the changes into SVN; please read the
    20   <xref linkend="intro-welcome-credits"/> page in Chapter 1 for details on
     20  <xref linkend="credits"/> page in Chapter 1 for details on
    2121  who wrote what.</para>
    2222
  • introduction/welcome/contact.xml

    r17be8c3 r4afc2603  
    66]>
    77
    8 <sect1 id="intro-welcome-contactinfo">
     8<sect1 id="contactinfo">
    99  <?dbhtml filename="contactinfo.html"?>
    1010
     
    1717
    1818  <para>Please direct your emails to one of the BLFS mailing lists. See
    19   <xref linkend="intro-welcome-maillists"/> for more information on
     19  <xref linkend="maillists"/> for more information on
    2020  the available mailing lists.</para>
    2121
     
    2525
    2626</sect1>
    27 
  • introduction/welcome/conventions.xml

    r17be8c3 r4afc2603  
    66]>
    77
    8 <sect1 id="intro-welcome-conventions">
     8<sect1 id="conventions">
    99  <?dbhtml filename="conventions.html"?>
    1010
     
    3232  <blockquote>
    3333    <para>This form of text (fixed width text) is showing screen
    34     output, probably as the result of commands issued and is also used to
     34    output, probably a result from issuing a command. It is also used to
    3535    show filenames such as <filename>/boot/grub/grub.conf</filename></para>
    3636  </blockquote>
     
    4848  <blockquote>
    4949    <para>This form of text is used for hypertext links external to
    50     the book such as HowTo's, download locations, websites, etc.</para>
     50    the book such as HowTos, download locations, websites, etc.</para>
    5151  </blockquote>
    5252
     
    8484
    8585  <blockquote>
    86     <para>This form of text is used to show a specific system user reference
    87     in the instructions.</para>
     86    <para>This form of text is used to show a specific system user or group
     87    reference in the instructions.</para>
    8888  </blockquote>
    8989
  • introduction/welcome/credits.xml

    r17be8c3 r4afc2603  
    66]>
    77
    8 <sect1 id="intro-welcome-credits" xreflabel="Credits">
     8<sect1 id="credits" xreflabel="Credits">
    99  <?dbhtml filename="credits.html"?>
    1010
  • introduction/welcome/maillists.xml

    r17be8c3 r4afc2603  
    66]>
    77
    8 <sect1 id="intro-welcome-maillists" xreflabel="Mailing lists">
     8<sect1 id="maillists" xreflabel="Mailing lists">
    99  <?dbhtml filename="maillists.html"?>
    1010
     
    2121
    2222  <para>For more information regarding which lists are available, how to
    23   subscribe to them, archive locations, etc. visit <ulink
    24   url="http://www.linuxfromscratch.org/mail.html"/>.</para>
     23  subscribe to them, archive locations, etc., visit
     24  <ulink url="http://www.linuxfromscratch.org/mail.html"/>.</para>
    2525
    2626</sect1>
  • introduction/welcome/mirrors.xml

    r17be8c3 r4afc2603  
    66]>
    77
    8 <sect1 id="intro-welcome-mirrors" xreflabel="Mirrors">
     8<sect1 id="mirrors" xreflabel="Mirrors">
    99  <?dbhtml filename="mirrors.html"?>
    1010
     
    1616  <title>Mirror Sites</title>
    1717
    18   <para>The BLFS project has a number of mirrors setup world-wide to make it
    19   easier and more convenient for you to access the website.  Please visit the
     18  <para>The BLFS project has a number of mirrors set up world-wide to make it
     19  easier and more convenient for you to access the website. Please visit the
    2020  <ulink url="http://www.linuxfromscratch.org/mirrors.html"/> website for the
    2121  list of current mirrors.</para>
    2222
    2323</sect1>
    24 
    25 
  • introduction/welcome/packages.xml

    r17be8c3 r4afc2603  
    66]>
    77
    8 <sect1 id="intro-welcome-packages" xreflabel="Getting the Source Packages">
     8<sect1 id="packages" xreflabel="Getting the Source Packages">
    99  <?dbhtml filename="packages.html"?>
    1010
  • introduction/welcome/version.xml

    r17be8c3 r4afc2603  
    66]>
    77
    8 <sect1 id="intro-welcome-version" xreflabel="Book Version">
     8<sect1 id="version" xreflabel="Book Version">
    99  <?dbhtml filename="version.html"?>
    1010
     
    1818  <para>This is BLFS-BOOK version &version; dated &releasedate;.
    1919  If this version is older than a month, a newer version is probably already
    20   available for download. Check one of the mirror sites below for updated
     20  available for download. Check one of the mirror sites at
     21  <ulink url="http://www.linuxfromscratch.org/mirrors.html"/> for updated
    2122  versions.</para>
    2223
    2324</sect1>
    24 
  • introduction/welcome/which.xml

    r17be8c3 r4afc2603  
    66]>
    77
    8 <sect1 id="intro-welcome-whichsections" xreflabel="Which sections of the book?">
     8<sect1 id="whichsections" xreflabel="Which sections of the book?">
    99  <?dbhtml filename="which.html"?>
    1010
     
    1717
    1818  <para>Unlike the Linux From Scratch book, BLFS isn't designed to be
    19   followed in a linear manner.  This is because LFS provides instructions
     19  followed in a linear manner. This is because LFS provides instructions
    2020  on how to create a base system which is capable of turning into anything
    21   from a web server to a multimedia desktop system.  BLFS is where we try
     21  from a web server to a multimedia desktop system. BLFS is where we try
    2222  to guide you in the process of going from the base system to your intended
    2323  destination. Choice is very much involved.</para>
    2424
    2525  <para>Everyone who reads the book will want to read certain sections.  The
    26   <xref linkend="introduction"/> part&ndash;which you are currently
    27   reading&ndash;contains generic information.  Especially take note of the
    28   information in Important Information (<xref linkend="intro-important"/>), as
    29   this contains comments about how to unpack software and various other aspects
    30   which apply throughout the book.</para>
     26  <xref linkend="introduction"/> part, which you are currently reading,
     27  contains generic information.  Especially take note of the information in
     28  <xref linkend="important"/>, as this contains comments about how to
     29  unpack software, issues related to using different locales and various other
     30  aspects which apply throughout the book.</para>
    3131
    3232  <para>The part on <xref linkend="postlfs"/> is where most people will want
     
    3939  system.</para>
    4040
    41 <para>Following these basic items, most people will want to at least browse
     41  <para>Following these basic items, most people will want to at least browse
    4242  through the <xref linkend="general"/> part of the book.  This part contains
    4343  information on many items which are prerequisites for other sections of the
    44   book as well as some items (such as Programming (<xref linkend="general-prog"/>)
     44  book as well as some items (such as <xref linkend="general-prog"/>)
    4545  which are useful in their own right.  Note that you don't have to install all
    4646  of these libraries and packages found in this part to start with, each
    47   BLFS install procedure tells you which packages
     47  BLFS installation procedure tells you which packages
    4848  it depends upon so you can choose the program you want to install and see
    4949  what it needs.</para>
     
    6161  more advanced network services.  These are dealt with in the <xref
    6262  linkend="server"/> part of the book.  Those wanting to build servers
    63   should find  a good starting point there.  Note that <xref linkend="server"/>
     63  should find a good starting point there.  Note that this section
    6464  also contains information on various database packages.</para>
    6565
    6666  <para>The next parts of the book principally deal with desktop systems.  This
    67   portion of the book starts with a part talking about <xref linkend="x"/>.  This
     67  portion of the book starts with a part talking about <xref linkend="x"/>. This
    6868  part also deals with some generic X-based libraries (<xref linkend="x-lib"/>).
    6969  After this, <xref linkend="kde"/> and <xref linkend="gnome"/> are given their
     
    8383
    8484</sect1>
    85 
Note: See TracChangeset for help on using the changeset viewer.