#[1]ALFS DTD [2]Preface

ALFS DTD

Version 3.1

ALFS DTD Development Team

   Copyright © 2001-2004 ALFS DTD Development Team

   All rights reserved.

   Redistribution and use in source and binary forms, with or without
   modification, are permitted provided that the following conditions are
   met:
     * Redistributions in any form must retain the above copyright
       notice, this list of conditions and the following disclaimer.
     * Neither the name of "Linux From Scratch", "Automated Linux From
       Scratch" nor the names of its contributors may be used to endorse
       or promote products derived from this material without specific
       prior written permission.
     * Any material derived from Linux From Scratch must contain a
       reference to the "Linux From Scratch" project.
     * Any material derived from Automated Linux From Scratch must
       contain a reference to the "Automated Linux From Scratch" project.

   THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
   ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
   LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
   A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR
   CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
   EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
   PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
   PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
   LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
   NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
   SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

   Abstract

   This book explains in detail how to use ALFS DTD v3.1.
     _________________________________________________________________

Dedication

   This book is dedicated to the LFS and ALFS communities.

   Table of Contents

   [3]Preface

        [4]ChangeLog
        [5]Who Would Want To Read This Book
        [6]Contact Information

              [7]Mailing Lists
              [8]News Server
              [9]WWW Links
              [10]Other

        [11]Acknowledgements
        [12]Conventions Used In This Book

   [13]1. Description of the ALFS Profile Syntax

        [14]ALFS DTD Introduction
        [15]XML & DTD Syntax

              [16]Quick Introduction to XML Syntax
              [17]Standard Entities
              [18]XML Elements and Attributes
              [19]Quick Introduction to DTD Syntax
              [20]DTD Element Declaration
              [21]DTD Attribute Declaration
              [22]DOCTYPE and SYSTEM Declarations

        [23]Element : <alfs>

              [24]Syntax
              [25]Description
              [26]Examples

        [27]Element : <archive>

              [28]Syntax
              [29]Description
              [30]Examples

        [31]Element : <base>

              [32]Syntax
              [33]Description
              [34]Examples

        [35]Element : <configure>

              [36]Syntax
              [37]Description
              [38]Example #1
              [39]Example #2
              [40]Example #3

        [41]Element : <content>

              [42]Syntax
              [43]Description
              [44]Examples

        [45]Element : <copy>

              [46]Syntax
              [47]Description
              [48]Examples

        [49]Element : <description>

              [50]Syntax
              [51]Description
              [52]Examples

        [53]Element: <destination>

              [54]Syntax
              [55]Description
              [56]Example #1
              [57]Example #2

        [58]Element: <digest>

              [59]Syntax
              [60]Description
              [61]Examples

        [62]Element: <download>

              [63]Syntax
              [64]Description
              [65]Examples

        [66]Element: <environment>

              [67]Syntax
              [68]Description
              [69]Examples

        [70]Element: <execute>

              [71]Syntax
              [72]Description
              [73]Example #1
              [74]Example #2

        [75]Element: <file>

              [76]Syntax
              [77]Description
              [78]Examples

        [79]Element: <find>

              [80]Syntax
              [81]Description
              [82]Examples

        [83]Element: <include>

              [84]Syntax
              [85]Description
              [86]Examples

        [87]Element: <item>

              [88]Syntax
              [89]Description
              [90]Examples

        [91]Element: <link>

              [92]Syntax
              [93]Description
              [94]Examples

        [95]Element: <list>

              [96]Syntax
              [97]Description
              [98]Examples

        [99]Element: <make>

              [100]Syntax
              [101]Description
              [102]Example #1
              [103]Example #2

        [104]Element: <mkdir>

              [105]Syntax
              [106]Description
              [107]Examples

        [108]Element: <move>

              [109]Syntax
              [110]Description
              [111]Examples

        [112]Element: <name>

              [113]Syntax
              [114]Description
              [115]Examples

        [116]Element: <option>

              [117]Syntax
              [118]Description
              [119]Examples

        [120]Element: <ownership>

              [121]Syntax
              [122]Description
              [123]Example #1
              [124]Example #2

        [125]Element: <package>

              [126]Syntax
              [127]Description
              [128]Examples

        [129]Element: <packageinfo>

              [130]Syntax
              [131]Description
              [132]Examples

        [133]Element: <para>

              [134]Syntax
              [135]Description
              [136]Examples

        [137]Element: <param>

              [138]Syntax
              [139]Description
              [140]Examples

        [141]Element: <patch>

              [142]Syntax
              [143]Description
              [144]Examples

        [145]Element: <permissions>

              [146]Syntax
              [147]Description
              [148]Examples

        [149]Element: <prefix>

              [150]Syntax
              [151]Description
              [152]Examples

        [153]Element: <reference>

              [154]Syntax
              [155]Description
              [156]Examples

        [157]Element: <remove>

              [158]Syntax
              [159]Description
              [160]Examples

        [161]Element: <replace>

              [162]Syntax
              [163]Description
              [164]Examples

        [165]Element: <requires>

              [166]Syntax
              [167]Description
              [168]Examples

        [169]Element: <root>

              [170]Syntax
              [171]Description
              [172]Examples

        [173]Element: <search_replace>

              [174]Syntax
              [175]Description
              [176]Examples

        [177]Element: <source>

              [178]Syntax
              [179]Description
              [180]Examples

        [181]Element: <stage>

              [182]Syntax
              [183]Description
              [184]Examples

        [185]Element: <stageinfo>

              [186]Syntax
              [187]Description
              [188]Examples

        [189]Element: <target>

              [190]Syntax
              [191]Description
              [192]Examples

        [193]Element: <textdump>

              [194]Syntax
              [195]Description
              [196]Example #1
              [197]Example #2

        [198]Element: <unpack>

              [199]Syntax
              [200]Description
              [201]Examples

        [202]Element: <url>

              [203]Syntax
              [204]Description
              [205]Examples

        [206]Element: <user>

              [207]Syntax
              [208]Description
              [209]Examples

        [210]Element: <utilizes>

              [211]Syntax
              [212]Description
              [213]Examples

        [214]Element: <variable>

              [215]Syntax
              [216]Description
              [217]Examples

        [218]Element: <version>

              [219]Syntax
              [220]Description
              [221]Examples

Preface

ChangeLog

   3.1 - June 17th, 2004
     * June 17th, 2004 [jwrober]: Released v3.1.

Who Would Want To Read This Book

   This book is mainly aimed at those who want more information on the
   ALFS DTD. The DTD is designed to be implementation agnostic. This
   means that you may be reading this book as part of an ALFS
   implementation source tarball or on the ALFS website.

Contact Information

Mailing Lists

   The ALFS DTD uses two mailing list hosted from the Linux From Scratch
   servers.

   Please direct the majority of your emails to the ALFS mailing list at
   [222]alfs-discuss@linuxfromscratch.org. This is an excellent place to
   post questions and bug reports. For complete mailing list information,
   refer to
   [223]http://www.linuxfromscratch.org/mailman/listinfo/alfs-discuss.

   The second list is really for the development team's use and is
   available at [224]alfs-log@linuxfromscratch.org. This is an excellent
   place to see the daily activity of the project. For complete mailing
   list information, refer to
   [225]http://www.linuxfromscratch.org/mailman/listinfo/alfs-log.

News Server

   All the mailing lists hosted at linuxfromscratch.org are also
   accessible via the NNTP server. All messages posted to a mailing list
   will be copied to its correspondent newsgroup, and vice versa.

   The news server can be reached at [226]news.linuxfromscratch.org.

WWW Links

   Some other xrefs that might interest you:

   Linux From Scratch:

     [227]http://www.linuxfromscratch.org

   Automated Linux From Scratch:

     [228]http://www.linuxfromscratch.org/alfs

Other

   The current ALFS DTD documentation maintainer is James Robertson. If
   you need to reach James, send an email to
   [229]jwrober@linuxfromscratch.org.

Acknowledgements

   We would like to thank the following people and organizations for
   their contributions towards the Automated Linux From Scratch project:
     * [230]Vassili Dzuba <vassili@linuxfromscratch.org> -- for helping
       to create the DTD and writing the intial version of this book.
     * [231]Gerard Beekmans <gerard@linuxfromscratch.org> -- for being
       more then a great help.
     * [232]James Robertson <jwrober@linuxfromscratch.org> -- Current
       documentation editor.
     * Jesse Tien-Ten-Que for helping to create the DTD and writing the
       initial version of this book.
     * Countless other people on the ALFS mailing list who are making
       this project happen by giving their suggestions, testing the tools
       and submitting bug reports.

Conventions Used In This Book

   To make things easy to follow, there are a number of conventions used
   throughout the book. Following are some examples :
./configure --prefix=/usr

     This form of text is designed to be typed in exactly as seen unless
     otherwise noted in the surrounding text.

   install-info: unknown option '--dir-file=/mnt/lfs/usr/info/dir'

     This form of text (fixed width text) is showing screen output,
     probably as the result of commands issued and is also used to show
     filenames such as /bin/grep

   Emphasis

   Bold Emphasis

     These forms of text are used for several purposes in the book but
     mainly to emphasize important points or to give examples as to what
     to type.

   [233]http://www.linuxfromscratch.org/alfs

     This form of text is used for hyperxrefs, both within the book and
     to external pages such as HowTo's, download locations, websites,
     etc.

cat > $LFS/etc/group <<"EOF"
        root:x:0:
        bin:x:1:
        ......
EOF

     This type of section is used mainly when creating configuration
     files. The first command (in bold) tells the system to create the
     file $LFS/etc/group from whatever is typed on the following lines
     until the sequence EOF is encountered. Therefore, this whole
     section is generally typed as seen.

Note

   Sample Note

     This type of section is to define a notice of some kind. Mostly to
     alert you of something to take note of.

Chapter 1. Description of the ALFS Profile Syntax

ALFS DTD Introduction

   ALFS profiles are written using an XML syntax. This chapter describes
   the various XML elements that can occur in a profile.

   For each element, the book describes:
     * the formal definition of the element, using the exact DTD syntax.
     * a description of the element.
     * one or several examples.
     * an equivalent bash script(s) for the examples (when applicable).

XML & DTD Syntax

Quick Introduction to XML Syntax

   To ensure that all readers of the ALFS DTD Book get as much as
   possible from its contents, it is necessary to provide a quick
   introduction to the concepts of XML and DTD syntax.

Note

   This introduction provides very few examples. This book is written in
   an XML DTD called DocBook XML. For an example of XML just look at the
   book's source. Since this book is documenting an XML DTD, look at the
   rest of the book's contents for examples of DTD syntax.

   To begin, here are some basic rules of XML :
     * XML documents use a self-describing and simple to use syntax.
     * All XML elements must have a closing tag. With XML, it is illegal
       to omit the closing tag.
     * XML tags are case sensitive.
     * All XML elements must be properly nested. Improper nesting of tags
       makes no sense to XML.
     * All XML documents must have a root element. In other words, all
       XML documents must contain a single tag pair to define a root
       element.
     * Attribute values must always be quoted. With XML, it is illegal to
       omit quotation marks around attribute values.
     * XML parsers preserve all whitespace in XML documents, even that
       which is considered non-significant.
     * The use of the ampersand [ & ] symbol is reserved. XML uses this
       to define an entity reference.

Standard Entities

   As mentioned in the last section, the ampersand symbol cannot be used
   by itself. There are a set of standard entity references that every
   DTD file should contain. There are mostly symbols that you would want
   to place inside the XML file. You define them by using thier decimal
   value on the ASCII chart. Here is a good list :
     * Less-Than [ < ] : "&#60;"
     * Greater-Than [ > ] : "&#62;"
     * Ampersand [ & ] : "&#38;"
     * Apostrophe [ ' ] : "&#39;"
     * Quote [ " ] : "&#34;"
     * Non Breaking Space (a forced space) : "&#32;"
     * Emdash [ -- ] : "&#045;&#045;"

   Generally, you can assume that amp, lt, gt, and apos are predefined,
   but you can always make sure by using the numeric references above.
   Also, if you ever need to create your own, you know how to do it now.

XML Elements and Attributes

   XML is designed to hold any kind of information. This information is
   stored in Elements. Elements are the basic building blocks of XML and
   are represented in a XML document as tag pairs. Attributes provide a
   mechanism to further define or classify an element. Elements have
   relationships with other elements in a document. Some are parents and
   some are children. Using this semantic description, one can see that
   children elements need parent elements defined and used first. As
   mentioned in the last section, an XML document must have a root
   element. Think of this as the ultimate parent element. The root
   element must be defined and used before all other elements and all
   sub-elements (children). All elements and sub-elements will reside
   inside of the root element. An element can have parsed content, mixed
   content, simple content, empty content or attributes in their
   definition.

   XML elements must follow these naming rules :
     * Names can contain letters, numbers, and other characters
     * Names must not start with a number or punctuation character
     * Names must not start with the letters xml (or XML or Xml ...)
     * Names cannot contain spaces

Quick Introduction to DTD Syntax

   Once an XML document is written, it is generally a good idea to
   validate the elements used in the document against a known DTD. The
   Document Type Definition is the mechanism with which one validates the
   content of a well-formed XML document.

   XML DTD files contain :
     * Element declarations and definitions : Elements are declared and
       defined with their relationships in the DTD file.
     * Attribute declarations and definitions : Element classes or
       attributes are declared and defined in the DTD file.
     * Entities : Entities are the same thing as variables inside a DTD
       file or XML document. They can hold any kind of data.
     * PCDATA : PCDATA is Parsed Character DATA. PCDATA is text that will
       be parsed by a parser. Tags inside the text will be treated as
       markup and entities will be expanded.
     * CDATA : CDATA is Character DATA. CDATA is text that will NOT be
       parsed by a parser. Tags inside the text will NOT be treated as
       markup and entities will not be expanded.

DTD Element Declaration

   Elements are declared in the DTD file using a simple, but strict
   syntax. There are four ways to define an element :
     * EMPTY : When an element is declared with the EMPTY keyword, it
       means that the element will not hold any information. This is
       generally used for special tags like <br>.
     * ANY : When an element is declared with the ANY keyword, it means
       that the element can contain any information that the author wants
       it to. This is generally a special case.
     * Character Data : When an element is declared with either the
       PCDATA or CDATA keywords, it will hold one of the two types of
       information described above.
     * With Children : When an element is declared with the names of
       other elements in it, this defines a parent-child relationship.
       Look in the DTD for the child element names to be further defined
       with the other three ways.
     * Mixed : Some combination of the above four. Generally this is
       character data mixed with children.

   When an element is declared with children, it will also define how the
   children can be used inside an XML document and also in the order that
   they are allowed to appear in an XML document. There are four ways
   that children elements can be defined in a DTD file :
     * One Occurance Only : Example : [234]Element: <search_replace>. The
       child elements of <search_replace> -- <file>, <find>, and
       <replace> can only be used once. Notice that there are no symbols
       after any of the child element names. This is the identifier.
     * Minimum of One Occurance : Example : [235]Element: <permissions>.
       One of the child elements of <permissions> -- <name>, must be used
       a minimum of once, but can also be used many times. Notice the
       plus [ + ] symbol after the name. This is the identifier.
     * Zero or More Occurances : Example : [236]Element: <download>. One
       of the child elements of <download> -- <url>, can be used zero or
       many times. Notice the asterisk [ * ] symbol after the name. This
       is the identifier.
     * Zero or One Occurance : Example : [237]Element: <download>. One of
       the child elements of <download> -- <digest>, can be used zero or
       one time only. Notice the question mark [ ? ] symbol after the
       name. This is the identifier.
     * Either / Or Occurances : Example : [238]Element: <execute>. One of
       the two child elements of <execute> -- <param>, or <prefix>, can
       only be used. Notice the pipe [ | ] symbol in between the two
       elements. This is the identifier.

DTD Attribute Declaration

   As mentioned above, attributes can help to define "classes" of
   Elements. Attributes are defined with types and values. There are 11
   types :
     * CDATA : The value is Character Data.
     * (en1|en2|...) : The value is an enumerated list.
     * ID : The value is a unique id.
     * IDREF : The value is the id of another element.
     * IDREFS : The value is a list of other ids,
     * NMTOKEN : The value is a valid XML name.
     * NMTOKENS : The value is a list of valid XML names.
     * ENTITY : The value is an entity.
     * ENTITIES : The value is a list of entities.
     * NOTATION : The value is a name of a notation.
     * xml : The value is a predefined XML value.

   There are four value options :
     * Value : The default value of the attribute surrounded by quotes [
       " " ]. Example : [239]Element : <alfs>.
     * #IMPLIED : The attribute is optional. Example : [240]Element :
       <alfs>.
     * #REQUIRED : The attribute is required when the element is used.
       Example : [241]Element: <execute>.
     * #FIXED : A fixed value. Used with the Value option. Example :
       [242]Element : <alfs>.

DOCTYPE and SYSTEM Declarations

   The DOCTYPE declaration is used in an XML document to define to the
   XML parser what DTD should be referenced. This declaration is helpful
   when you have a seperate DTD file outside of the XML document. See
   [243]Element : <alfs> for an example.

   The SYSTEM declaration is used in an XML document to give provide a
   way to split up a file into smaller chunks. Many XML files can be
   quite large and having all the information inside one file can be
   unwieldy. The SYSTEM declaration works just like any ENTITY
   declaration. See [244]Element : <alfs> for an example.

Element : <alfs>

Syntax

<!ELEMENT alfs           ((configure | copy | download | execute | link |
                           make | mkdir | move | ownership | package |
                           patch | permissions | remove | search_replace |
                           stage | textdump | unpack | include)+)>
<!ATTLIST alfs
          base           CDATA #IMPLIED
          version        CDATA #FIXED "3.1"
          xml:base       CDATA #IMPLIED
          xmlns:xi       CDATA #IMPLIED>

   See also : [245]Element : <configure> | [246]Element : <copy> |
   [247]Element: <download> | [248]Element: <execute> | [249]Element:
   <link> | [250]Element: <make> | [251]Element: <mkdir> | [252]Element:
   <move> | [253]Element: <ownership> | [254]Element: <package> |
   [255]Element: <patch> | [256]Element: <permissions> | [257]Element:
   <remove> | [258]Element: <search_replace> | [259]Element: <stage> |
   [260]Element: <textdump> | [261]Element: <unpack> | [262]Element:
   <include>

Description

   The alfs element is the root element of an ALFS profile document. This
   means that an ALFS profile should contain one and only one alfs
   element with all the other elements being embedded (used) within this
   element.

   When processing an alfs element, you processes all its embedded
   children in their order of occurrence.

   The base attribute allows you to specify the directory in which the
   operation will be performed. For a better description, see
   [263]Element : <base>.

   The version attribute identifies the version of the ALFS profile
   syntax used; it should be "3.1".

   The include element and the xml:base and xmlns:xi attributes allow you
   to use xi:include directives in your profile(s).

Examples

<!DOCTYPE alfs SYSTEM "alfs-3.1.dtd" [

        <!ENTITY % general_entities SYSTEM "entities/general">

        %general_entities;

]>

<alfs version="3.1">

 .....

</alfs>

   There is no equivalent Bash script example for this element.

Element : <archive>

Syntax

<!ELEMENT archive        (#PCDATA)>

   This element occurs in : [264]Element: <unpack>.

Description

   The archive element is used to specify the archive file in an unpack
   operation.

Examples

   Refer to [265]Element: <unpack> for an example.

Element : <base>

Syntax

<!ELEMENT base           (#PCDATA)>

   This element occurs in : [266]Element: <stageinfo>

   This element occurs as an attribute in the elements : [267]Element :
   <alfs> | [268]Element : <configure> | [269]Element : <copy> |
   [270]Element: <execute> | [271]Element: <link> | [272]Element: <make>
   | [273]Element: <mkdir> | [274]Element: <move> | [275]Element:
   <ownership> | [276]Element: <patch> | [277]Element: <permissions> |
   [278]Element: <search_replace> | [279]Element: <textdump>

Description

   The base element when used as an element specifies the base directory
   which will be used by all the commands in the stage (inherited),
   unless another base is specified at the level of the command as an
   attribute.

   The base element when used as an attribute specifies the base
   directory which will be used by any parent element it was called from.

Important

   It is very important to understand the difference between the two
   uses. Most importantly understand that the base element/attribute has
   no effect on the parent element it is used in unless relative paths
   are used in the parent element's other attributes and child elements.

Examples

<stage name="Install gzip">

        <stageinfo>

                <root>/mnt/lfs</root>
                <user>lfs</user>
                <environment>
                        <variable name="PATH">/bin:/sbin</variable>
                </environment>
                <base>/usr/src/gzip.1.2.4a</base>

        </stageinfo>

        <configure>
        </configure>

        <make>
        </make>

        <make>
                <param>install</param>
        </make>

</stage>

   The equivalent bash script is :
echo Executing configure
su - lfs
export PATH=/bin:/sbin
cd /usr/src/gzip.1.2.4a
./configure

echo Executing make
su - lfs
export PATH=/bin:/sbin
cd /usr/src/gzip.1.2.4a
make

echo Executing make
su - lfs
export PATH=/bin:/sbin
cd /usr/src/gzip.1.2.4a
make install

echo Exiting stage

Element : <configure>

Syntax

<!ELEMENT configure      ((param | prefix)*)>
<!ATTLIST configure
          base           CDATA #IMPLIED
          command        CDATA #IMPLIED>

   This element occurs in : [280]Element : <alfs> | [281]Element: <stage>

   See also : [282]Element: <param> | [283]Element: <prefix>

Description

   The configure element is one of the top-level operation elements. The
   configure element is used to describe the configure command.

   When processing the element, you execute the command ./configure with
   the parameter(s) and prefix(es) specified.

   The base attribute allows you to specify the directory in which the
   operation will be performed. For a better description, see
   [284]Element : <base>.

   The command attribute allows you to specify a custom command if you
   don't want to use the default ./configure. This is extremely useful
   when running ./configure in a build directory outside the main source
   directory. The packages gcc and glibc often require this.

Example #1

   This first example calls configure without any parameters :
<configure base="/usr/src/mypackage/">
</configure>

   The equivalent bash script is :
echo Executing configure
cd /usr/src/mypackage/
./configure

Example #2

   This second example calls configure with some prefixes and a parameter
   :
<configure base="/usr/src/mypackage/">
        <prefix>CFLAGS="..."<prefix>
        <prefix>CXXFLAGS="..."<prefix>
        <param>--prefix=/opt/mypackage</param>
</configure>

   The equivalent bash script is :
echo Executing configure
cd /usr/src/mypackage/
CFLAGS="..." CXXFLAGS="..." ./configure --prefix=/opt/mypackage

Example #3

   This third example calls configure with a parameter and uses prefix :
<configure base="/usr/src/mypackage/">
        <prefix>PATH=/usr/local/bin</prefix>
        <param>--prefix=/opt/mypackage</param>
</configure>

   The equivalent bash script is :
echo Executing configure
cd /usr/src/mypackage/
PATH=/usr/local/bin ./configure --prefix=/opt/mypackage

Element : <content>

Syntax

<!ELEMENT content        (#PCDATA)>

   This element occurs in : [285]Element: <textdump>.

Description

   The content element is used to specify the content of the file being
   created when processing a textdump operation.

Note

   Of course, it is possible to use XML entity references in the #PCDATA
   or string of this element.

Examples

<textdump base="/etc">

        <file>group</file>

        <content>
                =root:x:0:
                =bin:x:1:
                =sys:x:2:
                =kmem:x:3:
                =tty:x:4:
                =tape:x:5:
                =daemon:x:6:
                =floppy:x:7:
                =disk:x:8:
                =lp:x:9:
                =dialout:x:10:
                =audio:x:11:
        </content>

</textdump>

   The equivalent bash script is :
echo Generating file group
cd /etc
cat > group << 'EOF'
root:x:0:
bin:x:1:
sys:x:2:
kmem:x:3:
tty:x:4:
tape:x:5:
daemon:x:6:
floppy:x:7:
disk:x:8:
lp:x:9:
dialout:x:10:
audio:x:11:
EOF

Element : <copy>

Syntax

<!ELEMENT copy           (option*, source+, destination)>
<!ATTLIST copy
          base           CDATA #IMPLIED>

   This element occurs in : [286]Element : <alfs> | [287]Element: <stage>

   See also : [288]Element: <option> | [289]Element: <source> |
   [290]Element: <destination>

Description

   The copy element is one of the top-level operation elements and is
   used to copy one or more files and/or directories to a specified
   destination.

   The option child-element provides a means to pass an option to the cp
   command.

Note

   Not all of the cp command's options are in every implementation. Refer
   to the documentation for your implementation to determine what options
   are available.

   The source child-element is required and can be used multiple times to
   provide multiple source files and/or directories.

   The destination child-element is required and can only be used once. A
   copy can only have one destination.

   The base attribute allows you to specify the directory in which the
   operation will be performed. For a better description, see
   [291]Element : <base>.

Examples

<copy base="/usr/src/mypackage">
        <option>force</option>
        <source>config.txt</source>
        <destination>/opt/mypackage/config.txt</destination>
</copy>

   The equivalent bash script is :
echo Copying 'config.txt into /opt/mypackage/config.txt'
cd /usr/src/mypackage
cp -f config.txt /opt/mypackage/config.txt

Element : <description>

Syntax

<!ELEMENT description    (para | list)*>

   This element occurs in : [292]Element: <packageinfo>

   See also : [293]Element: <para> | [294]Element: <list>

Description

   The description element contains the description of a package. Its use
   is for documentation only.

Examples

   Refer to [295]Element: <packageinfo> for an example.

   There is no equivalent Bash script example for this element.

Element: <destination>

Syntax

<!ELEMENT destination    (#PCDATA)>

   This element occurs in : [296]Element : <copy> | [297]Element:
   <download> | [298]Element: <move> | [299]Element: <unpack> |

Description

   The destination element is used to specify the name of the destination
   file or directory when processing an element in which it occurs.

Example #1

   The first example is an unpack command.
<unpack>
        <archive>/usr/src/lfs-packages/gzip.1.2.4a.tar.gz</archive>
        <destination>/usr/src</destination>
</unpack>

   The equivalent bash script is :
echo Unpacking /usr/src/lfs-packages/gzip.1.2.4a.tar.gz into /usr/src
cd /usr/src
tar -xzvf /usr/src/lfs-packages/gzip.1.2.4a.tar.gz

Example #2

   The second example is a copy command.
<copy base="/usr/src/mypackage">
        <option>force</option>
        <source>config.txt</source>
        <destination>/opt/mypackage/config.txt</destination>
</copy>

   The equivalent bash script is :
echo Copying 'config.txt into /opt/mypackage/config.txt'
cd /usr/src/mypackage
cp -f  config.txt /opt/mypackage/config.txt

Element: <digest>

Syntax

<!ELEMENT digest         (#PCDATA)>
<!ATTLIST digest
          type           CDATA "md5">

   This element occurs in ; [300]Element: <download> | [301]Element:
   <unpack>

Description

   The digest element is used to specify a unique digest of the file to
   be operated on by the parent element. Typically these digests are MD5
   sums, but an ALFS implementation can support alternative digests as
   well, including SHA-1.

Note

   Support for the digest element is implementation specific. Not all
   implementations will support every type of digest hash available.
   Refer to the documentation for your implementation to determine what
   options are available.

   The type attribute specifies the algorithm used to create the
   specified digest value, and defaults to MD5 if not specified.

Examples

   Refer to [302]Element: <reference> for an example.

   There is no equivalent Bash script example for this element.

Element: <download>

Syntax

<!ELEMENT download       (file, url*, destination, digest?)>

   This element occurs in : [303]Element : <alfs> | [304]Element: <stage>

   See also : [305]Element: <file> | [306]Element: <url> | [307]Element:
   <destination> | [308]Element: <digest>

Description

   The download element is one of the top-level operation elements. It is
   used to specify one or several URLs from which a file can be
   downloaded; optionally a digest to check that the file being
   downloaded is the right one and was downloaded correctly (not
   corrupted or truncated).

   The file child-element contains the name of the file to be downloaded.

   The url child-element contains the url of the directory from which the
   download is performed. It should be terminated by a slash [ / ]. More
   precisely, the actual URL used for the download is the catenation of
   the content of the url element with the content of the file element.

   The destination child-element contains the path of the directory into
   which the download should be performed.

   The digest child-element contains the value to which the digest
   computed from the dowloaded file will be compared. See [309]Element:
   <digest>.

   If the file is already present in the destination directory, no
   download is performed but the digest is checked if specified.

Examples

<download>
        <file>gzip-1.2.4a.tar.gz</file>
        <url>ftp://gnu.org/</url>
        <destination>/tmp/</destination>
</download>

   The equivalent bash script is :
echo Executing 'download'
wget -nc -O /tmp/gzip-1.2.4a.tar.gz ftp://gnu.org/gzip-1.2.4a.tar.gz

Element: <environment>

Syntax

<!ELEMENT environment    (variable+)>
<!ATTLIST environment
          mode           (append | prepend) #IMPLIED>

   This element occurs in : [310]Element: <stageinfo>

   See also : [311]Element: <variable>

Description

   The environment element allows you to define one or more environment
   variables to be added to the system environment used when calling the
   commands of the stage to which it applies.

   By default, the supplied value replaces any existing value for the
   specified variable. The mode attribute allows you to specify whether
   the supplied value should be prepended or appended to the existing
   value.

Examples

<stage>
        <stageinfo>

                <base>/usr/src/gzip.1.2.4a</base>

                <environment>
                        <variable name="GCCFLAGS">-O2</variable>
                        <variable name="PATH" mode="prepend">/usr/src/gzip.1.2.
4a:</variable>
                        <variable name="LDFLAGS" mode="append"> -s</variable>
                </environment>

        </stageinfo>

</stage>

   The equivalent bash script is :
echo Stage

export GCCFLAGS=-O2
export PATH=/usr/src/gzip.1.2.4a:$PATH
export LDFLAGS="$LDFLAGS -s"

echo Exiting stage

Element: <execute>

Syntax

<!ELEMENT execute        ((param | prefix)*)>
<!ATTLIST execute
          base           CDATA #IMPLIED
          command        CDATA #REQUIRED>

   This element occurs in : [312]Element : <alfs> | [313]Element: <stage>

   See also : [314]Element: <param> | [315]Element: <prefix>

Description

   The execute element is one of the top-level operation elements. It is
   used to execute any arbitrary system command.

   The param child-element contains parameters for the command.

   The prefix child-element contains any prefix data for the command to
   execute.

   The base attribute allows you to specify the directory in which the
   operation will be performed. For a better description, see
   [316]Element : <base>.

   The command attribute contains the text of the command itself.

Example #1

   The first example is an execute command without a parameter.
<execute command="umount">

   The equivalent bash script is :
echo Executing 'umount'
umount

Example #2

   The second example is an execute command with one parameter.
<execute command="mount">
        <param>/mount/lfs</param>
</execute>

   The equivalent bash script is :
echo Executing 'mount'
mount /mount/lfs

Element: <file>

Syntax

<!ELEMENT file           (#PCDATA)>

   This element occurs in : [317]Element: <download> | [318]Element:
   <search_replace> | [319]Element: <textdump>.

Description

   The file element is used to specify the filename for a download,
   search_replace or textdump operation.

Examples

   See any one of the parent elements for an example.

Element: <find>

Syntax

<!ELEMENT find           (#PCDATA)>

   This element occurs in : [320]Element: <search_replace>

Description

   The find element allows you to specify the string to be searched for
   in a search and replace operation.

Examples

   Refer to the parent [321]Element: <search_replace> for an example.

Element: <include>

Syntax

<!ELEMENT include        EMPTY>
<!ATTLIST include
          href           CDATA #REQUIRED>

   This element occurs in : [322]Element : <alfs>

Description

   The include element contains data necessary to handle the xi:include
   directive in an alfs element.

Examples

   Refer to [323]Element : <alfs> for an example.

Element: <item>

Syntax

<!ELEMENT item           (#PCDATA)>

   This element occurs in : [324]Element: <list>

Description

   The item element contains an item within a list in a description
   element.

Examples

   Refer to [325]Element : <description> for an example.

Element: <link>

Syntax

<!ELEMENT link           (option?, target+, name)>
<!ATTLIST link
          base           CDATA #IMPLIED
          type           CDATA #IMPLIED>

   This element occurs in : [326]Element : <alfs> | [327]Element: <stage>

   See also : [328]Element: <option> | [329]Element: <target> |
   [330]Element: <name>

Description

   The link element is one of the top-level operation elements. It allows
   you to create a hard or symbolic link.

   The target child-element gives the name(s) of the target.

   The option child-element provides a means to pass an option to the ln
   command.

Note

   Not all of the ln command's options are in every implementation. Refer
   to the documentation for your implementation to determine what options
   are available.

   The name child-element gives the name of the link. When there are
   several targets, this must be the name of a directory, in which the
   links to the targets will be created.

   The base attribute allows you to specify the directory in which the
   operation will be performed. For a better description, see
   [331]Element : <base>.

   The type attribute generally can have one of two values: "symbolic" or
   "hard" to go along with how the ln works.

Examples

<link type="symbolic">
        <target>share/man</target>
        <target>share/doc</target>
        <target>share/info</target>
        <name>/usr/local</name>
</link>

   The equivalent bash script is :
echo 'Linking  share/man share/doc share/info into /usr/local'
ln -s  share/man share/doc share/info /usr/local

Element: <list>

Syntax

<!ELEMENT list           (item | list)+>
<!ATTLIST list
          type           (bullet | number) "bullet">

   This element occurs in : [332]Element : <description>

   See also : [333]Element: <item>

Description

   The list element contains a list of items or sub-lists in a
   description.

   The type attribute provides a way to define a numbered or bulleted
   list

Examples

   Refer to the parent [334]Element : <description> for an example.

Element: <make>

Syntax

<!ELEMENT make           ((param | prefix)*)>
<!ATTLIST make
          base           CDATA #IMPLIED>

   This element occurs in : [335]Element : <alfs> | [336]Element: <stage>

   See also : [337]Element: <param> | [338]Element: <prefix>

Description

   The make element is one of the top-level operation elements. It
   describes the make command.

   The param child-element allows you to specify parameters of the make
   command.

   The prefix child-element allows you to specify an environment variable
   or some other prefix to the make command

   The base attribute allows you to specify the directory in which the
   operation will be performed. For a better description, see
   [339]Element : <base>.

Example #1

   The first example is a make without parameter
<make />

   The equivalent bash script is :
echo Executing make
make

Example #2

   The second example is a make with a parameter
<make base="/usr/src/mypackage">
        <param>install</param>
</make>

   The equivalent bash script is :
echo Executing make
cd /usr/src/mypackage
make install

Element: <mkdir>

Syntax

<!ELEMENT mkdir          (option?, permissions?, name+)>
<!ATTLIST mkdir
          base           CDATA #IMPLIED>

   This element occurs in : [340]Element : <alfs> | [341]Element: <stage>

   See also : [342]Element: <option> | [343]Element: <name> |
   [344]Element: <permissions>

Description

   The mkdir element is one of the top-level operation elements. It
   describes the creation of one (or several) directory(ies).

   The option child-element provides a means to pass an option to the
   mkdir command.

Note

   Not all of the mkdir command's options are in every implementation.
   Refer to the documentation for your implementation to determine what
   options are available.

   The permissions child-element assigns permissions to the directories
   created by the command following the syntax in [345]Element:
   <permissions>.

   The name child-element contains the name(s) of the directory(ies) to
   be created.

   The base attribute allows you to specify the directory in which the
   operation will be performed. For a better description, see
   [346]Element : <base>.

Examples

<mkdir base="/usr/local/lib">
        <option>parents</option>
        <name>X11</name>
</mkdir>

   The equivalent bash script is :
cd /usr/local/lib
echo Making directory X11
mkdir -p X11

Element: <move>

Syntax

<!ELEMENT move           (option?, source+, destination)>
<!ATTLIST move
          base           CDATA #IMPLIED>

   This element occurs in : [347]Element : <alfs> | [348]Element: <stage>
   |

   See also : [349]Element: <option> | [350]Element: <source> |
   [351]Element: <destination>

Description

   The move element is one of the top-level operation elements. It can be
   used to move one or more files and/or directories into a destination
   directory, or to rename a single file or directory.

   The option child-element provides a means to pass an option to the mv
   command.

Note

   Not all of the mv command's options are in every implementation. Refer
   to the documentation for your implementation to determine what options
   are available.

   When processing this element, you move each source to the destination,
   using the specified option if present.

   The source child-element contains the name of the source file and its
   directory.

   The destination child-element contains the name of the destination
   directory (and, optionally, the command) for the mv command.

   The base attribute allows you to specify the directory in which the
   operation will be performed. For a better description, see
   [352]Element : <base>.

Examples

<move>
        <source>/usr/src/mypackage/config.txt</source>
        <destination>/opt/mypackage/config.txt</destination>
</move>

   The equivalent bash script is :
echo Move ' /usr/src/mypackage/config.txt /opt/mypackage/config.txt'
mv /usr/src/mypackage/config.txt /opt/mypackage/config.txt

Element: <name>

Syntax

<!ELEMENT name           (#PCDATA)>

   This element occurs in : [353]Element: <link> | [354]Element: <mkdir>
   | [355]Element: <ownership> | [356]Element: <permissions> |
   [357]Element: <requires> | [358]Element: <utilizes>

   See also (used as an attribute) : [359]Element: <package> |
   [360]Element: <stage> | [361]Element: <variable>

Description

   The name element is used to specify a name for those commands that
   requires it.

Examples

<mkdir base="/usr/local/lib">
        <option>parents</option>
        <name>X11</name>
</mkdir>

   The equivalent bash script is :
cd /usr/local/lib
echo Making directory X11
mkdir -p X11

Element: <option>

Syntax

<!ELEMENT option         (#PCDATA)>

   This element occurs in : [362]Element : <copy> | [363]Element: <link>
   | [364]Element: <mkdir> | [365]Element: <move> | [366]Element:
   <ownership> | [367]Element: <permissions>

Description

   The option element allows you to specify an option of the parent
   element.

Examples

<mkdir base="/usr/local/lib">
        <option>parents</option>
        <name>X11</name>
</mkdir>

   The equivalent bash script is :
cd /usr/local/lib
echo Making directory X11
mkdir -p X11

Element: <ownership>

Syntax

<!ELEMENT ownership      (option?, name+)>
<!ATTLIST ownership
          base           CDATA #IMPLIED
          user           CDATA #IMPLIED
          group          CDATA #IMPLIED>

   This element occurs in : [368]Element : <alfs> | [369]Element: <stage>

   See also : [370]Element: <option> | [371]Element: <name>

Description

   The ownership element is one of the top-level operation elements. It
   is used to perform a group and/or user ownership change on a file or
   set of files

   The option child-element provides a means to pass an option to the
   chown command.

Note

   Not all of the chown command's options are in every implementation.
   Refer to the documentation for your implementation to determine what
   options are available.

   The name child-element contains the name of the file (or directory)
   whose ownership is to be changed. This child-element can accept both
   names and group numbers.

   The base attribute allows you to specify the directory in which the
   operation will be performed. For a better description, see
   [372]Element : <base>.

   The user attribute specifies the name of the user which will own the
   file or directory. This child-element can accept both names and user
   numbers. See [373]Element: <user>.

   The group attribute specifies the name of the group which will own the
   file or directory.

Example #1

   The first example uses symbolic names.
<ownership user="root" group="root">
        <option>recursive</option>
        <name>/etc/rc.d</name>
        <name>/etc/sysconfig</name>
</ownership>

   The equivalent bash script is :
echo Changing group of /etc/rc.d to root
chgrp -R root /etc/rc.d

echo Changing owner of /etc/rc.d to root
chown -R root /etc/rc.d

echo Changing group of /etc/sysconfig to root
chgrp -R root /etc/sysconfig

echo Changing owner of /etc/sysconfig to root
chown -R root /etc/sysconfig

Example #2

   The second example uses numeric values (0 = root).
<ownership user="0" group="0">
        <option>recursive</option>
        <name>/etc/rc.d</name>
        <name>/etc/sysconfig</name>
</ownership>

   The equivalent bash script is :
echo Changing group of /etc/rc.d to 0
chgrp -R 0 /etc/rc.d

echo Changing owner of /etc/rc.d to 0
chown -R 0 /etc/rc.d

echo Changing group of /etc/sysconfig to 0
chgrp -R 0 /etc/sysconfig

echo Changing owner of /etc/sysconfig to 0
chown -R 0 /etc/sysconfig

Element: <package>

Syntax

<!ELEMENT package        (packageinfo?, stage+)>
<!ATTLIST package
          name           CDATA #REQUIRED
          version        CDATA #REQUIRED>

   This element occurs in : [374]Element : <alfs> | [375]Element: <stage>

   See also : [376]Element: <packageinfo> | [377]Element: <stage>

Description

   The package element is one of the top-level operation elements. It
   describes the build process of a package. The actual build process is
   described by the stage sub-elements.

   The name attribute contains the name of the package. See [378]Element:
   <name>.

   The version attribute contains the version of the package. See
   [379]Element: <version>.

Examples

<package name="zlib" version="1.1.4">

        <stage name="Unpacking a package.">

                <unpack>
                        <archive>/usr/src/lfs-packages/zlib.1.1.4.tar.gz</archi
ve>
                        <destination>/usr/src</destination>
                </unpack>

        </stage>

        .....

</package>

   The equivalent bash script is :
echo Generating package zlib 1.1.4

#-----------------------------------------
echo Stage "Unpacking a package."

echo Unpacking /usr/src/lfs-packages/zlib.1.1.4.tar.gz into /usr/src
cd /usr/src
[[ $? != 0 ]] &&  echo Command failed && exit 3

tar xzvf /usr/src/lfs-packages/zlib.1.1.4.tar.gz
[[ $? != 0 ]] &&  echo Command failed && exit 3


echo Exiting stage "Unpacking a package."

.....

echo End of generating package zlib 1.1.4

Element: <packageinfo>

Syntax

<!ELEMENT packageinfo    (description?, requires*, utilizes*)>

   This element occurs in : [380]Element: <package>

   See also : [381]Element : <description> | [382]Element: <requires> |
   [383]Element: <utilizes>

Description

   The packageinfo element groups elements containing information about
   the package, namely a description and some dependency relationship(s).

   The description child-element provides for a description of the
   packge.

   The requires child-element provides for a relationship (dependancy) to
   other defined packages in the profile.

   The utilizes child-element provdes for a relationship (uses /
   optional) to other defined packages in the profile.

Examples

<package name="gimp" version="1.2.3">

        <packageinfo>

                <description>

                        <para>The gimp package contains the GNU Image Manipulat
ion Program.
                                    This is useful for :</para>

                        <list>
                                <item>photo retouching,</item>
                                <item>image composition,</item>
                                <item>image authoring.</item>
                        </list>

                </description>

                <requires><name>gtk+</name></requires>

                <utilizes><name>libtiff</name></utilizes>
                <utilizes><name>libpng</name></utilizes>
                <utilizes><name>libjpeg</name></utilizes>
                <utilizes><name>aalib</name></utilizes>
                <utilizes><name>mpeg_lib</name></utilizes>
                <utilizes><name>python</name></utilizes>

        </packageinfo>

        ....

</package>

   There is no equivalent bash script for the element.

Element: <para>

Syntax

<!ELEMENT para           (#PCDATA)>

   This element occurs in : [384]Element : <description>

Description

   The para element contains a paragraph of documentary text.

Examples

   Refer to [385]Element: <packageinfo> for an example.

Element: <param>

Syntax

<!ELEMENT param          (#PCDATA)>

   This element occurs in : [386]Element : <configure> | [387]Element:
   <execute> | [388]Element: <make> | [389]Element: <patch>

Description

   This element is used to specify a parameter for the parent element.

Examples

<make>
        <param>install</param>
</make>

   The equivalent bash script is :
echo Executing make
make install

Element: <patch>

Syntax

<!ELEMENT patch          ((param | prefix)*)>
<!ATTLIST patch
          base           CDATA #IMPLIED>

   This element occurs : [390]Element : <alfs> | [391]Element: <stage>

   See also : [392]Element: <param> | [393]Element: <prefix>

Description

   The patch element is one of the top-level operation elements. It is
   used to execute the patch command.

   The param child-element contains the parameters of the command.

   The prefix child-element provides a means to specify an environment
   variable or some other prefix to the patch command.

   The base attribute allows you to specify the directory in which the
   operation will be performed. For a better description, see
   [394]Element : <base>.

Examples

<patch>
        <param>-N</param>
        <param>-p1</param>
        <param>-i ../gawk-3.1.1.patch</param>
</patch>

   The equivalent bash script is :
echo 'patch -N -p1 -i ../gawk-3.1.1.patch'
patch -N -p1 -i ../gawk-3.1.1.patch

Element: <permissions>

Syntax

<!ELEMENT permissions    (option?, name+)>
<!ATTLIST permissions
          base           CDATA #IMPLIED
          mode           CDATA #REQUIRED>

   See also : [395]Element: <option> | [396]Element: <name>

Description

   The permissions element is one of the top-level operation elements. It
   allows you to change the permissions of a (set of) file(s) or
   directory(ies).

   The option child-element provides a means to pass an option to the
   chmod command.

Note

   Not all of the chmod command's options are in every implementation.
   Refer to the documentation for your implementation to determine what
   options are available.

   The name child-element contains the name(s) of the files whose
   permission is to be modified. See [397]Element: <name>.

   The base attribute allows you to specify the directory in which the
   operation will be performed. For a better description, see
   [398]Element : <base>.

   The mode attribute gives the new access mode, as used in the chmod
   command.

Examples

<permissions mode="755">
        <name>/usr/bin/lex</name>
</permissions>

   The equivalent bash script is :
echo Changing permissions of /usr/bin/lex to 755
chmod 755 /usr/bin/lex

Element: <prefix>

Syntax

<!ELEMENT prefix         (#PCDATA)>

   This element occurs in : [399]Element : <configure> | [400]Element:
   <execute> | [401]Element: <make> | [402]Element: <patch>

Description

   The prefix element provides a means to specify an environment variable
   or some other prefix to the parent element.

Examples

   See any one of the parent elements for an example.

Element: <reference>

Syntax

<!ELEMENT reference      (#PCDATA)>

   This element occurs in : [403]Element: <unpack>

Description

   The reference element is used to specify the URL of the reference
   archive to download if the local copy is not available.

Examples

<unpack>
        <reference>ftp://ftp.gnu.org/gnu/gzip/gzip.1.2.4a.tar.gz</reference>
        <archive>/usr/src/lfs-packages/gzip.1.2.4a</archive>
        <destination>/usr/src</destination>
</unpack>

   The equivalent bash script is :
echo Unpacking /usr/src/lfs-packages/gzip.1.2.4a.tar.gz into /usr/src
[[ ! -f /usr/src/lfs-packages/gzip.1.2.4a.tar.gz ]] &&
  echo Retrieving  ftp://ftp.gnu.org/gnu/gzip/gzip.1.2.4a.tar.gz
[[ ! -f /usr/src/lfs-packages/gzip.1.2.4a.tar.gz ]] &&
  wget -O /usr/src/lfs-packages/gzip.1.2.4a.tar.gz ftp://ftp.gnu.org/gnu/gzip/g
zip.1.2.4a.tar.gz
[[ ! -f /usr/src/lfs-packages/gzip.1.2.4a.tar.gz ]] &&
  echo Archive does not exist && exit 3

cd /usr/src
tar xzvf /usr/src/lfs-packages/gzip.1.2.4a.tar.gz

Element: <remove>

Syntax

<!ELEMENT remove         (#PCDATA)>

   This element occurs in : [404]Element : <alfs> | [405]Element: <stage>

Description

   The remove element is one of the top-level operation elements. It
   allows you to remove a file or directory. The content of the element
   contains the name of the file.

Note

   Not all of the rm command's options are in every implementation. Refer
   to the documentation for your implementation to determine what options
   are available.

Examples

<remove>/usr/src/mypackage</remove>

   The equivalent bash script is :
echo Removing /usr/src/mypackage
rm -rf /usr/src/mypackage

Element: <replace>

Syntax

<!ELEMENT replace        (#PCDATA)>

   This element occurs in : [406]Element: <search_replace>

Description

   The replace element allows you to specify the replacement string in a
   search and replace operation.

Examples

   Refer to [407]Element: <search_replace> for an example.

Element: <requires>

Syntax

<!ELEMENT requires       (name, version*)>

   This element occurs in : [408]Element: <packageinfo>

   See also : [409]Element: <name> | [410]Element: <version>

Description

   The requires element denotes a dependency between two packages. The
   package containing the requires element depends on the package whose
   name is contained in the name child-element.

   The actual name is put into a name child-element.

Note

   To work properly, the package identified in the name child-element
   must be defined in either the same profile as the requires element, or
   in an additional profile (if the ALFS implementation you are using
   supports loading multiple profiles).

   The version element can be used to specify the allowable version(s) of
   the required package.

Examples

   Refer to [411]Element: <packageinfo> for an example.

Element: <root>

Syntax

<!ELEMENT root           (#PCDATA)>

   This element occurs in : [412]Element: <stageinfo>

Description

   The root element allows you to specify the name of a directory which
   will be the root directory for the commands of the stage.

Examples

<stage>
        <stageinfo>
                <root>/mnt/lfs</root>
                <base>/usr/src/gzip.1.2.4a</base>
        </stageinfo>

        <configure />

        <make />

        <make>
                <param>install</param>
        </make>
</stage>

   The equivalent bash script is :
echo Creating file /mnt/lfs/_nalfs_tmp.1...
cat > /mnt/lfs/_nalfs_tmp.1 << 'EOF1'
echo Executing configure
cd /usr/src/gzip.1.2.4a
./configure

echo Executing make
cd /usr/src/gzip.1.2.4a
make

echo Executing make
cd /usr/src/gzip.1.2.4a
make install

true
EOF1

chmod 775 /mnt/lfs/_nalfs_tmp.1
echo Executing in directory /mnt/lfs
/usr/sbin/chroot /mnt/lfs sh -c ./_nalfs_tmp.1

echo Exiting stage

Element: <search_replace>

Syntax

<!ELEMENT search_replace (file, find, replace)>
<!ATTLIST configure
          base           CDATA #IMPLIED>

   This element occurs in : [413]Element : <alfs> | [414]Element: <stage>

   See also : [415]Element: <file> | [416]Element: <find> | [417]Element:
   <replace>

Description

   The search_replace element is one of the top-level operation elements.
   It is used to perform a search and replace operation of a file on a
   file's contents.

   The file child-element contains the filename.

   The find child-element contains the string to be searched.

   The replace child-element contains the replacement string.

   The base attribute allows you to specify the directory in which the
   operation will be performed. For a better description, see
   [418]Element : <base>.

Examples

<search_replace base="/usr/src/mypackage">
        <file>runit.sh</file>
        <find>BINDIR</find>
        <replace>/bin</replace>
</search_replace>

   The equivalent bash script is :
echo Performing substitution in runit.sh
cd /usr/src/mypackage
cp runit.sh /tmp/foo.$$
sed -e 's/BINDIR/\/bin/' /tmp/foo.$$ > runit.sh

Element: <source>

Syntax

<!ELEMENT source         (#PCDATA)>

   This element occurs : [419]Element : <copy> | [420]Element: <move>

Description

   The source element is used to specify the name of the source in the
   parent element.

Examples

   See any one of the parent elements for an example.

Element: <stage>

Syntax

<!ELEMENT stage          (stageinfo?, (alfs | configure | copy | download |
                             execute | link | make | mkdir | move | ownership |
                             package | patch | permissions | remove |
                             search_replace | stage | textdump | unpack)*)>
<!ATTLIST stage
          name           CDATA #IMPLIED>

   This element occurs in : [421]Element : <alfs> | [422]Element: <stage>

   See also : [423]Element : <alfs> | [424]Element : <configure> |
   [425]Element : <copy> | [426]Element: <download> | [427]Element:
   <execute> | [428]Element: <link> | [429]Element: <make>> |
   [430]Element: <mkdir> | [431]Element: <move> | [432]Element:
   <ownership> | [433]Element: <package> | [434]Element: <patch> |
   [435]Element: <permissions> | [436]Element: <remove> | [437]Element:
   <search_replace> | [438]Element: <stageinfo> | [439]Element:
   <textdump> | [440]Element: <unpack>

Description

   The stage element is one of the top-level operation elements. It
   allows you to regroup commands, give a name to this group (through the
   name attribute) and optionally modify the execution context through
   the element stageinfo.

Examples

<stage>
        <stageinfo>
                <base>/usr/src/gzip.1.2.4a</base>
        </stageinfo>

        <configure />

        <make />

        <make>
                <param>install</param>
        </make>
</stage>

   The equivalent bash script is :
echo Executing configure
cd /usr/src/gzip.1.2.4a
./configure

echo Executing make
cd /usr/src/gzip.1.2.4a
make

echo Executing make
cd /usr/src/gzip.1.2.4a
make install

echo Exiting stage

Element: <stageinfo>

Syntax

<!ELEMENT stageinfo      (root?, user?, environment?, base?)>

   This element occurs in : [441]Element: <stage>

   See also : [442]Element: <root> | [443]Element : <base> |
   [444]Element: <environment> | [445]Element: <user>

Description

   The stageinfo element allows you to specify several contexts of
   information used to process the commands of the stage to which the
   stageinfo element belongs.

   The user child-element specifies a user ID that will be used as the
   effective user ID of the current process for all the commands of the
   stage. See [446]Element: <user>.

   The root child-element specifies a directory name in which the
   commands of the stage will be performed (using a chroot command). See
   [447]Element: <root>.

   The environment child-element allows you to specify an environment
   variable that will be added to the current environment when processing
   the commands of the stage. See [448]Element: <environment>.

   The base attribute allows you to specify the directory in which the
   operation will be performed. For a better description, see
   [449]Element : <base>.

Examples

<stage name="Install gzip">

        <stageinfo>
                <root>/mnt/lfs</root>
                <user>lfs</user>
                <base>/usr/src/gzip.1.2.4a</base>
        </stageinfo>

        <configure>
        </configure>

        <make>
        </make>

        <make>
                <param>install</param>
        </make>

</stage>

   The equivalent bash script is :
echo Executing configure
su - lfs
cd /usr/src/gzip.1.2.4a
./configure

echo Executing make
su - lfs
cd /usr/src/gzip.1.2.4a
make

echo Executing make
su - lfs
cd /usr/src/gzip.1.2.4a
make install

echo Exiting stage

Element: <target>

Syntax

<!ELEMENT target         (#PCDATA)>

   This element occurs in : [450]Element: <link>

Description

   The target element describes a target of a link operation.

Examples

   Refer to [451]Element: <link> for an example.

Element: <textdump>

Syntax

<!ELEMENT textdump       (file, content)>
<!ATTLIST textdump
          base           CDATA #IMPLIED
          mode           CDATA #IMPLIED>

   This element occurs in : [452]Element : <alfs> | [453]Element: <stage>

   See also : [454]Element: <file> | [455]Element : <content>

Description

   The textdump element is one of the top-level operation elements. It
   allows you to create a text file containing specified text.

   The file child-element contains the name of the file to be created.

   The content child-element is used to specify the content of the file
   being created when processing a textdump operation. When processing
   the textual content of this element, one removes the leading blanks up
   to and including a '=' character.

   The base attribute allows you to specify the directory in which the
   operation will be performed. For a better description, see
   [456]Element : <base>.

   The mode attribute allows you to specify the append creation mode.

Example #1

<textdump base="/etc">

        <file>group</file>

        <content>
                =root:x:0:
                =bin:x:1:
                =sys:x:2:
                =kmem:x:3:
                =tty:x:4:
                =tape:x:5:
                =daemon:x:6:
                =floppy:x:7:
                =disk:x:8:
                =lp:x:9:
                =dialout:x:10:
                =audio:x:11:
        </content>
</textdump>

   The equivalent bash script is :
cd /etc
cat > group << 'EOF'
root:x:0:
bin:x:1:
sys:x:2:
kmem:x:3:
tty:x:4:
tape:x:5:
daemon:x:6:
floppy:x:7:
disk:x:8:
lp:x:9:
dialout:x:10:
audio:x:11:
EOF

Example #2

<textdump mode="append">

        <file>/etc/sysconfig/network</file>

        <content>
                =GATEWAY=192.168.123.254
                =GATEWAY_IF=eth0
        </content>

</textdump>

   The equivalent bash script is :
echo Generating file /etc/sysconfig/network
cat >> /etc/sysconfig/network << 'EOF'
GATEWAY=192.168.123.254
GATEWAY_IF=eth0
EOF

Element: <unpack>

Syntax

<!ELEMENT unpack         (digest?, reference*, archive, destination)>

   This element occurs in : [457]Element : <alfs> | [458]Element: <stage>

   See also : [459]Element : <archive> | [460]Element: <destination> |
   [461]Element: <digest> | [462]Element: <reference>

Description

   The unpack element is one of the top-level operation elements. It is
   used to unpack an archive into a destination directory.

   The reference child-element gives the URL of the archive; it is only
   used if the archive file is not available locally.

   The digest child-element gives the digest of the archive, using the
   digest type specified in the type attribute. See [463]Element:
   <digest>.

   The archive child-element gives the name of the archive, and the
   destination child-element gives the name of the directory in which the
   archive is unpacked.

Examples

<unpack>
        <reference>ftp://ftp.gnu.org/gnu/gzip/gzip.1.2.4a.tar.gz</reference>
        <archive>/usr/src/lfs-packages/gzip.1.2.4a.tar.gz</archive>
        <destination>/usr/src</destination>
</unpack>

   The equivalent bash script is :
echo Unpacking /usr/src/lfs-packages/gzip.1.2.4a.tar.gz into /usr/src
wget -nc -O /usr/src/lfs-packages/gzip-1.2.4a.tar.gz ftp://ftp.gnu.org/gnu/gzip
/gzip.1.2.4a.tar.gz
cd /usr/src
tar xzvf /usr/src/lfs-packages/gzip.1.2.4a.tar.gz

Element: <url>

Syntax

<!ELEMENT url            (#PCDATA)>

   This element occurs in : [464]Element: <download>

Description

   The url element allows you to specify the Uniform Resource Locator
   (URL) of the directory containing the file to be downloaded when
   processing a download element.

Examples

   Refer to [465]Element: <download> for an example.

   There is no equivalent Bash script example for this element.

Element: <user>

Syntax

<!ELEMENT user           (#PCDATA)>

   This element occurs in : [466]Element: <stageinfo>

   See also : [467]Element: <ownership>

Description

   The user element allows you to specify a user ID that will be the
   effective user ID when executing the commands of the stage to which it
   applies.

Examples

   Refer to [468]Element: <stageinfo> for an example.

Element: <utilizes>

Syntax

<!ELEMENT utilizes       (name, version*)>

   This element occurs in : [469]Element: <packageinfo>

   See also : [470]Element: <name> | [471]Element: <version>

Description

   The utilizes element indicates that the package containing the
   utilizes element utilizes the package whose name is contained in the
   name child-element, but does not depend on it (in which case the
   element requires should be used).

   The actual name is put into the name child-element.

Note

   To work properly, the package identified in the name child-element
   must be defined in either the same profile as the utilizes element, or
   in an additional profile (if the ALFS implementation you are using
   supports loading multiple profiles).

Examples

<package name="gimp" version="1.2.3">

        <packageinfo>

                <requires><name>gtk+</name></requires>

                <utilizes><name>libtiff</name></utilizes>
                <utilizes><name>libpng</name></utilizes>
                <utilizes><name>libjpeg</name></utilizes>
                <utilizes><name>aalib</name></utilizes>
                <utilizes><name>mpeg_lib</name></utilizes>
                <utilizes><name>python</name></utilizes>

        </packageinfo>

        .....

</package>

   There is no equivalent Bash script example for this element.

Element: <variable>

Syntax

<!ELEMENT variable       (#PCDATA)>
<!ATTLIST variable
          name           CDATA #REQUIRED
          mode           CDATA #IMPLIED>

   This element occurs in : [472]Element: <environment>

Description

   The variable element allows you to add a variable definition to the
   system environment.

   The name of the variable is given by the name attribute of the
   element.

   The value of the variable is given by the textual content of the
   element.

   The mode attribute can take the value "append", in which case the
   content of the element is appended to the value of the environment
   variable.

   The mode attribute can also take the value "prepend", in which case
   the content of the element is prepended to the value of the
   environment variable.

Examples

<stage>
        <stageinfo>
                <base>/usr/src/gzip.1.2.4a</base>
                <environment>
                        <variable name="GCCFLAGS">-O2</variable>
                        <variable name="PATH" mode="append">:/opt/foo</variable
>
                </environment>
        </stageinfo>

        <configure />

        <make />

        <make>
                <param>install</param>
        </make>
</stage>

   The equivalent bash script is :
echo Stage

export GCCFLAGS=-O2
export PATH=${PATH}:/opt/foo
echo Executing configure
cd /usr/src/gzip.1.2.4a
./configure

echo Executing make
cd /usr/src/gzip.1.2.4a
make

echo Executing make
cd /usr/src/gzip.1.2.4a
make install

echo Exiting stage

Element: <version>

Syntax

<!ELEMENT version        (#PCDATA)>
<!ATTLIST version
          condition      (eq | ne | gt | ge | lt | le) #REQUIRED>

   This element occurs : [473]Element: <package> | [474]Element:
   <requires> | [475]Element: <utilizes>

Description

   The version element describes a constraint on the version of an
   utilized or required package.

   The condition is satisfied if the comparison specified by the
   condition attribute applies between the actual version value of the
   package, and the value specified as the content of the element.

   When performing the comparison, the sequences of digits are compared
   numerically, while all the other characters are compared using their
   codes. Moreover, any substring is greater than the empty string.

   That means, for instance, that 2.0.10 is greater than 2.0.9, 2.0a is
   greater than 2.0 and 2.10 is greater than 2.1a.

Note

   The algorithm fails for reasonable interpretations of version numbers
   like 3.0 and 3.0beta. Intuitively, 3.0 is greater than 3.0beta, but
   the algorithm returns the opposite. To indicate for instance that the
   required package must have a version greater than 3.0, one would need
   two version elements, to require that the actual version be greater
   than or equal to 3.0, and that it be different from 3.0beta.

Examples

<packageinfo>
        <requires>
                <name>guile</name>
                <version condition="ge">1.5</version>
        </requires>
</packageinfo>

   This signifies that the package being build requires guile in its
   version 1.5 or more recent.

   There is no equivalent Bash script example for this element.

References

   1. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2452758
   2. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#preface
   3. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#preface
   4. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#preface-changelog
   5. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#preface-audience
   6. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#preface-contactinfo
   7. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2522610
   8. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2522833
   9. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2522855
  10. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2522888
  11. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#preface-acknowledgements
  12. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#preface-conventions
  13. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#alfs_dtd
  14. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#alfs_dtd-intro
  15. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#xml_dtd-syntax
  16. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2451961
  17. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2452076
  18. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2525074
  19. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2525142
  20. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2525249
  21. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2525576
  22. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2525820
  23. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
  24. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2524806
  25. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2527009
  26. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2527107
  27. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_archive
  28. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2525992
  29. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2526015
  30. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2526677
  31. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
  32. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2526582
  33. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2527684
  34. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2527740
  35. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_configure
  36. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2526053
  37. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2526414
  38. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2527527
  39. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2527569
  40. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2527614
  41. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_content
  42. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2527150
  43. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2528681
  44. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2528716
  45. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_copy
  46. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2527287
  47. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2527378
  48. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2528415
  49. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_description
  50. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2528640
  51. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2528308
  52. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2528325
  53. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_destination
  54. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2527846
  55. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2528191
  56. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2528208
  57. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2528246
  58. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_digest
  59. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2528023
  60. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2528055
  61. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2528140
  62. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_download
  63. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2529473
  64. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2529566
  65. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2530206
  66. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_environment
  67. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2530161
  68. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2529857
  69. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2529112
  70. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_execute
  71. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2529260
  72. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2529336
  73. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2530821
  74. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2530855
  75. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_file
  76. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2530137
  77. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2530103
  78. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2529067
  79. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_find
  80. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2529024
  81. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2528850
  82. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2530715
  83. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_include
  84. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2528883
  85. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2528908
  86. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2528967
  87. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_item
  88. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2530295
  89. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2530317
  90. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2530643
  91. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_link
  92. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2530604
  93. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2531864
  94. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2531966
  95. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_list
  96. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2530901
  97. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2531576
  98. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2531602
  99. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_make
 100. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2531515
 101. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2531783
 102. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2531845
 103. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2532578
 104. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_mkdir
 105. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2530992
 106. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2531353
 107. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2532370
 108. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_move
 109. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2532305
 110. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2531093
 111. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2533383
 112. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_name
 113. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2532256
 114. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2533057
 115. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2533074
 116. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_option
 117. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2533243
 118. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2533985
 119. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2534002
 120. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_ownership
 121. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2532226
 122. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2532184
 123. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2533712
 124. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2533774
 125. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_package
 126. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2533574
 127. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2532942
 128. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2532999
 129. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_packageinfo
 130. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2532774
 131. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2532856
 132. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2534650
 133. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_para
 134. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2534891
 135. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2534823
 136. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2534840
 137. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_param
 138. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2535461
 139. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2535025
 140. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2534237
 141. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_patch
 142. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2535422
 143. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2534437
 144. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2534504
 145. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_permissions
 146. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2534392
 147. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2534341
 148. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2536249
 149. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_prefix
 150. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2535282
 151. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2535042
 152. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2535059
 153. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_reference
 154. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2535137
 155. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2535160
 156. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2536129
 157. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_remove
 158. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2535926
 159. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2535954
 160. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2535813
 161. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_replace
 162. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2536079
 163. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2536015
 164. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2536032
 165. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_requires
 166. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2535748
 167. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2535583
 168. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2536815
 169. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_root
 170. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2536850
 171. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2536618
 172. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2536634
 173. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_search_replace
 174. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2536924
 175. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2536602
 176. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2537899
 177. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_source
 178. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2536287
 179. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2536316
 180. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2536525
 181. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 182. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2536357
 183. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2536453
 184. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2536484
 185. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stageinfo
 186. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2538172
 187. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2537525
 188. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2537623
 189. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_target
 190. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2537466
 191. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2537488
 192. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2538335
 193. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_textdump
 194. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2538431
 195. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2539409
 196. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2539489
 197. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2539535
 198. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_unpack
 199. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2537385
 200. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2539156
 201. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2539224
 202. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_url
 203. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2539092
 204. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2538560
 205. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2538583
 206. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_user
 207. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2538673
 208. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2539018
 209. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2539036
 210. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_utilizes
 211. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2538959
 212. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2538792
 213. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2540102
 214. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_variable
 215. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2538827
 216. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2538854
 217. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2540963
 218. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_version
 219. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2539735
 220. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2540003
 221. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#id2540702
 222. mailto:alfs-discuss@linuxfromscratch.org
 223. http://www.linuxfromscratch.org/mailman/listinfo/alfs-discuss
 224. mailto:alfs-log@linuxfromscratch.org
 225. http://www.linuxfromscratch.org/mailman/listinfo/alfs-log
 226. news:news.linuxfromscratch.org
 227. http://www.linuxfromscratch.org/
 228. http://www.linuxfromscratch.org/alfs
 229. mailto:jwrober@linuxfromscratch.org
 230. mailto:vassili@linuxfromscratch.org
 231. mailto:gerard@linuxfromscratch.org
 232. mailto:jwrober@linuxfromscratch.org
 233. http://www.linuxfromscratch.org/alfs
 234. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_search_replace
 235. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_permissions
 236. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_download
 237. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_download
 238. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_execute
 239. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 240. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 241. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_execute
 242. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 243. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 244. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 245. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_configure
 246. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_copy
 247. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_download
 248. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_execute
 249. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_link
 250. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_make
 251. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_mkdir
 252. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_move
 253. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_ownership
 254. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_package
 255. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_patch
 256. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_permissions
 257. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_remove
 258. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_search_replace
 259. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 260. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_textdump
 261. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_unpack
 262. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_include
 263. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
 264. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_unpack
 265. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_unpack
 266. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stageinfo
 267. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 268. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_configure
 269. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_copy
 270. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_execute
 271. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_link
 272. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_make
 273. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_mkdir
 274. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_move
 275. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_ownership
 276. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_patch
 277. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_permissions
 278. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_search_replace
 279. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_textdump
 280. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 281. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 282. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_param
 283. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_prefix
 284. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
 285. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_textdump
 286. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 287. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 288. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_option
 289. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_source
 290. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_destination
 291. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
 292. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_packageinfo
 293. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_para
 294. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_list
 295. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_packageinfo
 296. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_copy
 297. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_download
 298. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_move
 299. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_unpack
 300. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_download
 301. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_unpack
 302. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_reference
 303. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 304. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 305. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_file
 306. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_url
 307. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_destination
 308. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_digest
 309. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_digest
 310. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stageinfo
 311. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_variable
 312. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 313. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 314. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_param
 315. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_prefix
 316. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
 317. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_download
 318. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_search_replace
 319. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_textdump
 320. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_search_replace
 321. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_search_replace
 322. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 323. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 324. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_list
 325. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_description
 326. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 327. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 328. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_option
 329. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_target
 330. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_name
 331. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
 332. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_description
 333. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_item
 334. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_description
 335. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 336. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 337. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_param
 338. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_prefix
 339. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
 340. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 341. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 342. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_option
 343. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_name
 344. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_permissions
 345. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_permissions
 346. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
 347. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 348. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 349. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_option
 350. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_source
 351. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_destination
 352. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
 353. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_link
 354. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_mkdir
 355. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_ownership
 356. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_permissions
 357. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_requires
 358. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_utilizes
 359. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_package
 360. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 361. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_variable
 362. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_copy
 363. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_link
 364. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_mkdir
 365. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_move
 366. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_ownership
 367. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_permissions
 368. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 369. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 370. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_option
 371. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_name
 372. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
 373. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_user
 374. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 375. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 376. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_packageinfo
 377. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 378. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_name
 379. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_version
 380. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_package
 381. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_description
 382. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_requires
 383. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_utilizes
 384. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_description
 385. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_packageinfo
 386. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_configure
 387. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_execute
 388. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_make
 389. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_patch
 390. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 391. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 392. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_param
 393. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_prefix
 394. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
 395. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_option
 396. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_name
 397. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_name
 398. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
 399. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_configure
 400. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_execute
 401. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_make
 402. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_patch
 403. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_unpack
 404. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 405. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 406. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_search_replace
 407. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_search_replace
 408. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_packageinfo
 409. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_name
 410. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_version
 411. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_packageinfo
 412. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stageinfo
 413. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 414. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 415. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_file
 416. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_find
 417. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_replace
 418. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
 419. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_copy
 420. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_move
 421. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 422. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 423. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 424. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_configure
 425. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_copy
 426. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_download
 427. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_execute
 428. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_link
 429. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_make
 430. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_mkdir
 431. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_move
 432. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_ownership
 433. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_package
 434. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_patch
 435. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_permissions
 436. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_remove
 437. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_search_replace
 438. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stageinfo
 439. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_textdump
 440. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_unpack
 441. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 442. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_root
 443. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
 444. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_environment
 445. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_user
 446. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_user
 447. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_root
 448. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_environment
 449. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
 450. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_link
 451. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_link
 452. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 453. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 454. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_file
 455. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_content
 456. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_base
 457. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_alfs
 458. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stage
 459. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_archive
 460. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_destination
 461. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_digest
 462. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_reference
 463. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_digest
 464. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_download
 465. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_download
 466. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stageinfo
 467. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_ownership
 468. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_stageinfo
 469. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_packageinfo
 470. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_name
 471. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_version
 472. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_environment
 473. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_package
 474. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_requires
 475. file://localhost/home/kpfleming/syntax_doc/ALFS-SYNTAX-DOC-CVS-NOCHUNKS.html#elem_utilizes