Changeset b2a9f85


Ignore:
Timestamp:
09/21/2003 02:07:57 PM (18 years ago)
Author:
Larry Lawrence <larry@…>
Branches:
10.0, 10.1, 11.0, 6.0, 6.1, 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, ken/refactor-virt, krejzi/svn, lazarus, nosym, perl-modules, qt5new, systemd-11177, systemd-13485, trunk, v5_0, v5_0-pre1, v5_1, v5_1-pre1, xry111/git-date, xry111/git-date-for-trunk, xry111/git-date-test
Children:
c4f1401
Parents:
36f9a23
Message:

acronym tagging

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

Files:
11 edited

Legend:

Unmodified
Added
Removed
  • appendices/old/old.xml

    r36f9a23 rb2a9f85  
    11<appendix role="dsssl" id="appendices-old">
    22<?dbhtml filename="old.html" dir="appendices"?>
    3 <title>Packages which are no longer in the main BLFS Book</title>
     3<title>Packages which are no longer in the main <acronym>BLFS</acronym> Book</title>
    44
    55<para>This appendix contains packages which have been deprecated from the
    6 main BLFS book for one reason or another.  The reason for their removal has
    7 been added to the top of the package instructions.  Note that in general
    8 these instructions are no longer maintained and will probably be removed in
    9 future releases.</para>
     6main <acronym>BLFS</acronym> book for one reason or another.  The reason for
     7their removal has been added to the top of the package instructions.  Note that
     8in general these instructions are no longer maintained and will probably be
     9removed in future releases.</para>
    1010
    1111&gnome-common;
  • appendices/symlinks/symlinks.xml

    r36f9a23 rb2a9f85  
    11<appendix role="dsssl" id="appendices-symlinks">
    22<?dbhtml filename="symlinks.html" dir="appendices"?>
    3 <title>List of rc?.d symlinks used in LFS/BLFS</title>
     3<title>List of rc?.d symlinks used in <acronym>LFS</acronym>/<acronym>BLFS</acronym></title>
    44
    55<para>This section lists all of the symlinks used by the lfs-bootscripts
    66package (correct as of version <userinput>1.9</userinput>) and all of
    7 the scripts in the BLFS book.  This is for two reasons:  first, so that
    8 you can see at a glance which number we have used for each package, and
    9 second so that <emphasis>we</emphasis> can see which number we have
    10 used for each package!  Without this, it would make our lives more
     7the scripts in the <acronym>BLFS</acronym> book.  This is for two reasons: 
     8first, so that you can see at a glance which number we have used for each
     9package, and second so that <emphasis>we</emphasis> can see which number we
     10have used for each package!  Without this, it would make our lives more
    1111difficult (as we'd probably end up with conflicts).</para>
    1212
  • book/legalnotice.xml

    r36f9a23 rb2a9f85  
    11<legalnotice>
    22
    3 <para>Copyright (c) 2001-2003, BLFS Development Team</para>
     3<para>Copyright (c) 2001-2003, <acronym>BLFS</acronym> Development Team</para>
    44
    55<para>All rights reserved.</para>
  • connect/dhcp/dhcpcd/dhcpcd-exp.xml

    r36f9a23 rb2a9f85  
    22<title>Command explanations</title>
    33
    4 <para><userinput>patch -Np1 -i ../dhcpcd-&dhcpcd-version;.patch
    5 </userinput> : Dhcpcd unpatched puts all configuration and temporary
    6 files in <filename>/etc/dhcpc</filename>. This becomes very annoying
    7 when dhcpcd tells you it's running and it's not.  You look in
    8 <filename>/var/run</filename> for the pid file, but it's not there, the
    9 pid file that needs deleting is in <filename>/etc/dhcpc</filename>. This
    10 patch brings this program into FHS compliance, but more importantly,
    11 puts files where you expect them to be.</para>
     4<para><command>patch -Np1 -i ../dhcpcd-&dhcpcd-version;.patch
     5</command> : <application>Dhcpcd</application> unpatched puts all configuration
     6and temporary files in <filename>/etc/dhcpc</filename>. This becomes very
     7annoying when <application>dhcpcd</application> tells you it's running and it's
     8not.  You look in <filename>/var/run</filename> for the pid file, but it's not
     9there, the pid file that needs deleting is in <filename>/etc/dhcpc</filename>.
     10This patch brings this program into <acronym>FHS</acronym> compliance, but more
     11importantly, puts files where you expect them to be.</para>
    1212
    13 <para><userinput>--prefix=""</userinput> : There may be a good reason for
    14 abandoning the normal BLFS convention of using --prefix=/usr here.  If
    15 you are installing DHCP, it is likely that it is required during the
    16 boot process and <filename>/usr</filename> may be network mounted in which case, dhcpcd
    17 wouldn't be available due to being on the network!  Therefore, depending
    18 on your situation, you may want it to be installed in <filename>/sbin</filename> or <filename>/usr/sbin</filename>.  This command installs to <filename>/sbin</filename>.</para>
     13<para><command>--prefix=""</command> : There may be a good reason for
     14abandoning the normal <acronym>BLFS</acronym> convention of using --prefix=/usr
     15here.  If you are installing <acronym>DHCP</acronym>, it is likely that it is
     16required during the boot process and <filename>/usr</filename> may be network
     17mounted in which case, <command>dhcpcd</command> wouldn't be available due to
     18being on the network!  Therefore, depending on your situation, you may want it
     19to be installed in <filename>/sbin</filename> or <filename>/usr/sbin
     20</filename>.  This command installs to <filename>/sbin</filename>.</para>
    1921
    20 <para><userinput>--sysconfdir=/var/lib</userinput> : This command install
     22<para><command>--sysconfdir=/var/lib</command> : This command install
    2123configuration files in the <filename>/var/lib</filename>
    2224directory.</para>
    2325
    24 <para><userinput>--mandir=/usr/share/man</userinput> : This command
     26<para><command>--mandir=/usr/share/man</command> : This command
    2527install the man pages to the <filename>/usr/share/man</filename>
    2628directory.</para>
  • general/graphlib/imlib2.xml

    r36f9a23 rb2a9f85  
    11<sect1 id="imlib2" xreflabel="Imlib2-&imlib2-version;">
    2 <?dbhtml filename="imlib2.html" dir="basicnet"?>
     2<?dbhtml filename="imlib2.html" dir="general"?>
    33<title>Imlib2-&imlib2-version;</title>
    44
  • introduction/important/bootscripts.xml

    r36f9a23 rb2a9f85  
    11<sect1 id="intro-important-bootscripts">
    22<?dbhtml filename="bootscripts.html" dir="introduction"?>
    3 <title>Using BLFS bootscripts</title>
     3<title>Using <acronym>BLFS</acronym> bootscripts</title>
    44
    55<para>The scripts included for packages such as <xref linkend="gpm"/>
     
    77the lfs-bootscripts package from version 3.2 and later of the <acronym>
    88LFS</acronym> book. Note that this is lfs-bootscripts-1.6 and later (the old
    9 numbering changed as of LFS-3.2).  The scripts won't work with versions
    10 of <acronym>LFS</acronym> before 3.2 because of a change in their organization
    11 with the new scripts.  However, it should be trivial to adapt the scripts if
    12 needed for older <acronym>LFS</acronym> versions.</para>
     9numbering changed as of <acronym>LFS</acronym>-3.2).  The scripts won't work
     10with versions of <acronym>LFS</acronym> before 3.2 because of a change in their
     11organization with the new scripts.  However, it should be trivial to adapt the
     12scripts if needed for older <acronym>LFS</acronym> versions.</para>
    1313
    1414</sect1>
  • introduction/welcome/welcome.xml

    r36f9a23 rb2a9f85  
    11<chapter id="intro-welcome">
    22<?dbhtml filename="welcome.html" dir="introduction"?>
    3 <title>Welcome to BLFS</title>
     3<title>Welcome to <acronym>BLFS</acronym></title>
    44<para>The Beyond Linux From Scratch book is designed to carry on from
    55where the <acronym>LFS</acronym> book leaves off.  Unlike the <acronym>LFS
  • postlfs/config/config.xml

    r36f9a23 rb2a9f85  
    11<chapter id="postlfs-config">
    22<?dbhtml filename="config.html" dir="postlfs"?>
    3 <title>After LFS Configuration Issues</title>
     3<title>After <acronym>LFS</acronym> Configuration Issues</title>
    44
    5 <para>The intention of LFS is to provide a basic system which you can
    6 build upon.  There are several things, about tidying up the system,
    7 which many people wonder about once they have done the base install.
     5<para>The intention of <acronym>LFS</acronym> is to provide a basic system
     6which you can build upon.  There are several things, about tidying up the
     7system, which many people wonder about once they have done the base install.
    88We hope to cover these issues in this chapter.</para>
    99
  • postlfs/postlfs.xml

    r36f9a23 rb2a9f85  
    11<part id="postlfs" xreflabel="Post LFS Configuration and Extra Software">
    22<?dbhtml filename="postlfs.html" dir="postlfs"?>
    3 <title>Post LFS Configuration and Extra Software</title>
     3<title>Post <acronym>LFS</acronym> Configuration and Extra Software</title>
    44
    55&postlfs-config;
  • pst/typesetting/sgml.xml

    r36f9a23 rb2a9f85  
    11<chapter id="pst-sgml">
    22<?dbhtml filename="sgml.html" dir="pst"?>
    3 <title>Standard Generalized Markup Language (SGML)</title>
     3<title>Standard Generalized Markup Language (<acronym>SGML</acronym>)</title>
    44
    55&sgml-common;
  • pst/typesetting/xml.xml

    r36f9a23 rb2a9f85  
    11<chapter id="pst-xml">
    22<?dbhtml filename="xml.html" dir="pst"?>
    3 <title>Extensible Markup Language (XML)</title>
     3<title>Extensible Markup Language (<acronym>XML</acronym>)</title>
    44
    55&DocBook;
Note: See TracChangeset for help on using the changeset viewer.