doc: Clean up more documentation

Signed-off-by: Sol Jerome <solj@ices.utexas.edu>

git-svn-id: https://svn.mcs.anl.gov/repos/bcfg/trunk/bcfg2@5721 ce84e21b-d406-0410-9b95-82705330c041

6 files changed, 164 insertions, 130 deletions

diff --git a/doc/unsorted/altsrc.txt b/doc/unsorted/altsrc.txt
index 248405ebc..251781d28 100644
--- a/doc/unsorted/altsrc.txt
+++ b/doc/unsorted/altsrc.txt
@@ -6,34 +6,52 @@
 Fun and Profit using altsrc
 ===========================
 
-Altsrc is a generic, bcfg2-server-side mechanism for performing configuration entry name remapping for the purpose of data binding.
+Altsrc is a generic, bcfg2-server-side mechanism for performing
+configuration entry name remapping for the purpose of data binding.
 
 Use Cases
 =========
 
-* Equivalent configuration entries on different architectures with different names
-* Mapping entries with the same name to different bind results in a configuration (two packages with the same name but different types)
-* A single configuration entry across multiple specifications (multi-plugin, or multi-repo)
+* Equivalent configuration entries on different architectures with
+  different names
+
+* Mapping entries with the same name to different bind results in a
+  configuration (two packages with the same name but different types)
+
+* A single configuration entry across multiple specifications
+  (multi-plugin, or multi-repo)
 
 Examples
 ========
 
-* Consider the case of /etc/hosts on linux and /etc/inet/hosts on solaris. These files contain the same data in the same format, and should typically be synchronized, however, exist in different locations. Classically, one would need to create one entry for each in Cfg or TCheetah and perform manual synchronization. Or, you could use symlinks and pray. Altsrc is driven from the bundle side. For example:
+* Consider the case of /etc/hosts on linux and ``/etc/inet/hosts`` on
+  solaris. These files contain the same data in the same format,
+  and should typically be synchronized, however, exist in different
+  locations. Classically, one would need to create one entry for each in
+  Cfg or TCheetah and perform manual synchronization. Or, you could use
+  symlinks and pray. Altsrc is driven from the bundle side. For example:
 
   .. code-block:: xml
 
       <Bundle name='netinfo'>
          <Group name='solaris'>
-           <ConfigFile name='/etc/inet/hosts' altsrc='/etc/hosts'/>
+           <Path name='/etc/inet/hosts' altsrc='/etc/hosts'/>
          </Group>
          <Group name='linux'>
-           <ConfigFile name='/etc/hosts'/>
+           <Path name='/etc/hosts'/>
          </Group>
       </Bundle>
 
-  In this case, when a solaris host gets the 'netinfo' bundle, it will get the first !ConfigFile entry, which includes an altsrc parameter. This will cause the server to bind the entry as if it were a !ConfigFile called '/etc/hosts'. This configuration entry is still called '/etc/inet/hosts', and is installed as such.
+  In this case, when a solaris host gets the 'netinfo' bundle, it will
+  get the first Path entry, which includes an altsrc parameter. This
+  will cause the server to bind the entry as if it were a Path
+  called ``/etc/hosts``. This configuration entry is still called
+  ``/etc/inet/hosts``, and is installed as such.
 
-* On encap systems, frequently multiple packages of the same name, but of different types will exist. For example, there might be an openssl encap package, and an openssl rpm package. This can be dealt with using a bundle like:
+* On encap systems, frequently multiple packages of the same name, but
+  of different types will exist. For example, there might be an openssl
+  encap package, and an openssl rpm package. This can be dealt with
+  using a bundle like:
 
   .. code-block:: xml
 
@@ -42,30 +60,43 @@ Examples
          <Package name='openssl' altsrc='openssl-rpm'/>
       </Bundle>
 
-  This bundle will bind data for the packages "openssl-encap" and "openssl-rpm", but will be delivered to the client with both packages named "openssl" with different types.
+  This bundle will bind data for the packages "openssl-encap" and
+  "openssl-rpm", but will be delivered to the client with both packages
+  named "openssl" with different types.
 
-* Finally, consider the case where there exist complicated, but completely independent specifications for the same configuration entry but different groups of clients. The following bundle will allow the use of two different TCheetah templates /etc/firewall-rules-external and /etc/firewall-rules-internal for different clients based on their group membership.
+* Finally, consider the case where there exist complicated, but
+  completely independent specifications for the same configuration entry
+  but different groups of clients. The following bundle will allow the use
+  of two different TCheetah templates ``/etc/firewall-rules-external``
+  and ``/etc/firewall-rules-internal`` for different clients based on
+  their group membership.
 
   .. code-block:: xml
 
       <Bundle name='firewall'>
          ...
          <Group name='conduit'>
-           <ConfigFile name='/etc/firewall-rules' altsrc='/etc/firewall-rules-external'/>
+           <Path name='/etc/firewall-rules' altsrc='/etc/firewall-rules-external'/>
          </Group>
          <Group name='internal'>
-           <ConfigFile name='/etc/firewall-rules' altsrc='/etc/firewall-rules-internal'/>
+           <Path name='/etc/firewall-rules' altsrc='/etc/firewall-rules-internal'/>
          </Group>
       </Bundle>
 
-* Consider the case where a variety of files can be constructed by a single template (TCheetah or TGenshi). It would be possible to copy this template into the proper location for each file, but that requires proper synchronization upon modification and knowing up front what the files will all be called. Instead, the following bundle allows the use of a single template for all proper config file instances.
+* Consider the case where a variety of files can be constructed by a
+  single template (TCheetah or TGenshi). It would be possible to copy
+  this template into the proper location for each file, but that requires
+  proper synchronization upon modification and knowing up front what
+  the files will all be called. Instead, the following bundle allows
+  the use of a single template for all proper config file instances.
 
   .. code-block:: xml
 
       <Bundle name='netconfig'>
-        <ConfigFile name='/etc/sysconfig/network-scripts/ifcfg-eth0' altsrc='/etc/ifcfg-template'/>
-        <ConfigFile name='/etc/sysconfig/network-scripts/ifcfg-eth1' altsrc='/etc/ifcfg-template'/>
-        <ConfigFile name='/etc/sysconfig/network-scripts/ifcfg-eth2' altsrc='/etc/ifcfg-template'/>
+        <Path name='/etc/sysconfig/network-scripts/ifcfg-eth0' altsrc='/etc/ifcfg-template'/>
+        <Path name='/etc/sysconfig/network-scripts/ifcfg-eth1' altsrc='/etc/ifcfg-template'/>
+        <Path name='/etc/sysconfig/network-scripts/ifcfg-eth2' altsrc='/etc/ifcfg-template'/>
       </Bundle>
 
-  altsrc can be used as a parameter for any entry type, and can be used in any structure, including Bundler, Base, and SGenshi.
+  altsrc can be used as a parameter for any entry type, and can be used
+  in any structure, including Bundler and Base.
diff --git a/doc/unsorted/annotated_examples.txt b/doc/unsorted/annotated_examples.txt
index 99c6f774c..b5b7e6b4e 100644
--- a/doc/unsorted/annotated_examples.txt
+++ b/doc/unsorted/annotated_examples.txt
@@ -11,7 +11,8 @@ ntp example
 
 Author: Jason Pepas 
 
-Here is a series of example configurations for bcfg2, each introducing another layer of functionality.  
+Here is a series of example configurations for bcfg2, each introducing
+another layer of functionality.
 
 * After each change, run 'bcfg-repo-validate -v'.  
 * Run the server with 'bcfg2-server -v'.  
@@ -20,7 +21,8 @@ Here is a series of example configurations for bcfg2, each introducing another l
 package only
 ------------
 
-Our example starts with the bare minimum configuration setup.  We have a client, a profile group, a list of packages, and a base configuration.
+Our example starts with the bare minimum configuration setup.  We have
+a client, a profile group, a list of packages, and a base configuration.
 
 ::
 
@@ -77,7 +79,7 @@ Setup an etc directory structure, and add it to the base.::
     <Group name='fedora'>
     <Package name='ntp'/>
     <Service name='ntpd'/>
-    <ConfigFile name='/etc/ntp.conf'/>
+    <Path name='/etc/ntp.conf'/>
     </Group>
     </Base>
 
@@ -86,10 +88,10 @@ create a bundle
 
 The above configuration layout works fine for a single service, but
 that method of organization would quickly become a nightmare as you
-approach the number of packages, services, and config files required
-to represent a fully configured host.  Bundles allow the grouping of
-related configuration entries that are used to provide a single
-service. This is done for several reasons:
+approach the number of packages, services, and config files required to
+represent a fully configured host.  Bundles allow the grouping of related
+configuration entries that are used to provide a single service. This
+is done for several reasons:
 
 * Grouping related things in one place makes it easier to add those
   entries for a multiple groups of clients
@@ -102,20 +104,20 @@ service. This is done for several reasons:
   entity in that bundle is modified. This ensures that new
   configuration files and software are used after installation.
 
-The config file, package, and
-service are really all related components describing the idea of an
-ntp client, so they should be logically grouped together.  We use a
-bundle to accomplish this.::
+The config file, package, and service are really all related components
+describing the idea of an ntp client, so they should be logically
+grouped together.  We use a bundle to accomplish this.::
 
     # cat Bundler/ntp.xml
     <Bundle name='ntp' version='2.0'>
     <Package name='ntp'/>
     <Service name='ntpd'/>
-    <ConfigFile name='/etc/ntp.conf'/>
+    <Path name='/etc/ntp.conf'/>
     </Bundle>
 
 After this bundle is created, it must be associated with a group (or
-groups). Add a bundle child element to the group(s) which should install this bundle.::
+groups). Add a bundle child element to the group(s) which should install
+this bundle.::
 
 
     # cat Metadata/groups.xml
@@ -146,8 +148,8 @@ I added a new bundle:
 .. code-block: xml
 
     <Bundle name="mysql-server" version="3.0">
-       <ConfigFile name="/root/bcfg2-install/mysql/users.sh"/>
-       <ConfigFile name="/root/bcfg2-install/mysql/users.sql"/>
+       <Path name="/root/bcfg2-install/mysql/users.sh"/>
+       <Path name="/root/bcfg2-install/mysql/users.sql"/>
        <PostInstall name="/root/bcfg2-install/mysql/users.sh"/>
        <Package name="mysql-server-4.1"/>
        <Service name="mysql"/>
@@ -162,14 +164,17 @@ The `users.sh` script looks like this:
     mysql --defaults-extra-file=/etc/mysql/debian.cnf mysql \
         < /root/bcfg2-install/mysql/users.sql
 
-On debian there is a user account in `/etc/mysql/debian.cnf` automatically created, but you could also (manually) create a user in the database that has enough permissions and add the login information in a file yourself. This file looks like this::
+On debian there is a user account in ``/etc/mysql/debian.cnf``
+automatically created, but you could also (manually) create a user in
+the database that has enough permissions and add the login information
+in a file yourself. This file looks like this::
 
     [client]
     host     = localhost
     user     = debian-sys-maint
     password = XXXXXXXXXX
 
-The `users.sql` looks like this::
+The ``users.sql`` looks like this::
 
     DELETE FROM db;
     INSERT INTO db VALUES ('localhost', 'phpmyadmin', 'pma', 'Y', 'Y',
diff --git a/doc/unsorted/bundler_examples.txt b/doc/unsorted/bundler_examples.txt
index 88db94f56..442e9ce28 100644
--- a/doc/unsorted/bundler_examples.txt
+++ b/doc/unsorted/bundler_examples.txt
@@ -99,4 +99,4 @@ Examples
         <Path name='/etc/sysconfig/network-scripts/ifcfg-eth2' altsrc='/etc/ifcfg-template'/>
       </Bundle>
 
-  altsrc can be used as a parameter for any entry type, and can be used in any structure, including Bundler, Base, and SGenshi.
+  altsrc can be used as a parameter for any entry type, and can be used in any structure, including Bundler and Base.
diff --git a/doc/unsorted/configurationentries.txt b/doc/unsorted/configurationentries.txt
deleted file mode 100644
index a841d56c1..000000000
--- a/doc/unsorted/configurationentries.txt
+++ /dev/null
@@ -1,32 +0,0 @@
-.. -*- mode: rst -*-
-
-.. _unsorted-configurationentries:
-
-=====================
-Configuration Entries
-=====================
-
-This page describes the names and semantics of each of the configuration entries used by Bcfg2.
-
-Common non-POSIX entries
-========================
-
-|| '''!TagName''' || '''Description''' || '''Attributes''' ||
-|| Action || Command || name, command, when, timing ||
-|| Package || Software Packages || name, type, version, url ||
-|| !PostInstall || !PostInstall command || name ||
-|| Service || System Services || name, type, status, reload ||
-
-Bcfg2 >= 1.0.0: New unified POSIX entries
-=========================================
-
-In 1.0.0, there are new unified POSIX Path entries which prevent inconsistent configuration specifications of multiple entries for a given path. The following table describes the various types available for new `Path` entries.
-
-|| '''Type''' || '''Replacement/New''' || '''Description''' || '''Attributes''' ||
-|| device || New || Create block, character, and fifo devices || name, dev_type (block, char, fifo), owner, group, major/minor (for block or char devices) ||
-|| directory || Replaces Directory entries || Directories || name, owner, group, perms, prune ||
-|| file || Replaces !ConfigFile entries || Configuration File || name, owner, group, perms, encoding, empty ||
-|| hardlink || New || Create hardlinks || name, to ||
-|| nonexistent || New || Specify a path that should not exist || name ||
-|| permissions || Replaces Permissions entries || Permissions of POSIX entities || name, owner, group, perms ||
-|| symlink || Replaces !SymLink entries || !SymLinks || name, to ||
diff --git a/doc/unsorted/index.txt b/doc/unsorted/index.txt
index 02f09d640..f01aee67e 100644
--- a/doc/unsorted/index.txt
+++ b/doc/unsorted/index.txt
@@ -17,13 +17,6 @@ list below.
 * `NewDynamicReports`
 * `NewDynamicReportsInstallation`
 * `Plugins/Actions`
-* `Plugins/Bundler/examples/kernel.xml`
-* `Plugins/Bundler/examples/moab.xml`
-* `Plugins/Bundler/examples/nagios.xml`
-* `Plugins/Bundler/examples/ntp.xml`
-* `Plugins/Bundler/examples/snmpd.xml`
-* `Plugins/Bundler/examples/torque.xml`
-* `Plugins/Bundler/examples/yp.xml`
 * `Plugins/Ohai`
 * `Plugins/Snapshots`
 * `Plugins/TGenshi/examples/bcfg2_cron`
diff --git a/doc/unsorted/writing_specification.txt b/doc/unsorted/writing_specification.txt
index 083065f76..9fe847298 100644
--- a/doc/unsorted/writing_specification.txt
+++ b/doc/unsorted/writing_specification.txt
@@ -12,40 +12,63 @@ Bcfg2 specifications are logically divided in to three areas:
 * Abstract
 * Literal
 
-The metadata portion of the configuration assigns a client to its profile group and to its non profle groups.  The profile group is assigned in Metadata/clients.xml and the non profile group assignments are in Metadata/groups.xml.
-
-The group memberships contained in the metadata are then used to constuct an abstract configuration for the client. An abstract configuration for a client identifies the configuration entities (packages, configuration files, service, etc) that a client requires, but it does not identify them explicitly. For instance an abstract configuration may identify that a client needs the bcfg2 package with
+The metadata portion of the configuration assigns a client to its profile
+group and to its non profle groups. The profile group is assigned
+in Metadata/clients.xml and the non profile group assignments are in
+Metadata/groups.xml.
+
+The group memberships contained in the metadata are then used to constuct
+an abstract configuration for the client. An abstract configuration for
+a client identifies the configuration entities (packages, configuration
+files, service, etc) that a client requires, but it does not identify
+them explicitly. For instance an abstract configuration may identify
+that a client needs the bcfg2 package with
 
 .. code-block:: xml
 
     <Package name=bcfg2/>
 
-but this does not explicitly identify that an RPM package version 0.9.2 should be loaded from http://rpm.repo.server/bcfg2-0.9.2-0.1.rpm.  The abstract configuration is defined in the xml configuration files for the Base and Bundles plugins.
+but this does not explicitly identify that an RPM package version
+0.9.2 should be loaded from http://rpm.repo.server/bcfg2-0.9.2-0.1.rpm.
+The abstract configuration is defined in the xml configuration files
+for the Base and Bundles plugins.
 
-A combination of a clients metadata (group memberships) and abstract configuration is then used to generate the clients literal configuration.  For instance the above abstract configuration entry may generate a literal configuration of
+A combination of a clients metadata (group memberships) and abstract
+configuration is then used to generate the clients literal configuration.
+For instance the above abstract configuration entry may generate a
+literal configuration of
 
 
 .. code-block:: xml
 
     <Package name='bcfg2' version='0.9.2-0.1' type='yum'/>
 
-A clients literal configuration is generated by a number of plugins that handle the different configuration entities.
+A clients literal configuration is generated by a number of plugins that
+handle the different configuration entities.
 
 .. image:: specification_overview.png
 
 Dynamic Groups
 ==============
 
-Dynamic groups are likewise complex, and are covered on their own [wiki:DynamicGroups page]
+Dynamic groups are likewise complex, and are covered on their own
+[wiki:DynamicGroups page]
 
 Abstract Configuration (Structures)
 ===================================
 
-A clients Abstract Configuration is the inventory of configuration entities that should be installed on a client.  Two plugins provide the basis for the abstract configuration, the Bundler and Base.
+A clients Abstract Configuration is the inventory of configuration
+entities that should be installed on a client. Two plugins provide the
+basis for the abstract configuration, the Bundler and Base.
 
-The plugin Bundler builds descriptions of interrelated configuration entities.  These are typically used for the representation of services, or other complex groups of entities.
+The plugin Bundler builds descriptions of interrelated configuration
+entities. These are typically used for the representation of services,
+or other complex groups of entities.
 
-The Base provides a laundry list of configuration entities that need to be installed on hosts.  These entities are independent from one another, and can be installed individually without worrying about the impact on other entities.
+The Base provides a laundry list of configuration entities that need to
+be installed on hosts. These entities are independent from one another,
+and can be installed individually without worrying about the impact on
+other entities.
 
 Usage of Groups in Base and Bundles
 -----------------------------------
@@ -67,57 +90,39 @@ Group membership maybe negated.  See "Writing Bundles" for an example.
 Configuration Entity Types
 --------------------------
 
-Entities in the abstract configuration (and correspondingly in the literal configuration) can have one of several types.  In the abstract configuration, each of these entities only has a tag and the name attribute set.
+Entities in the abstract configuration (and correspondingly in the
+literal configuration) can have one of several types. In the abstract
+configuration, each of these entities only has a tag and the name
+attribute set.
 
-The types of Configuration Entities that maybe assigned to the abstract configuration are as follows:
+The types of Configuration Entities that maybe assigned to the abstract
+configuration are as follows:
 
-|| '' '''Tag''' '' || '' '''Description''' '' ||
-|| Package || Software Package ||
-|| !ConfigFile || Configuration File ||
-|| Service  || Persistent system services and daemons ||
-|| Directory || File system Directories ||
-|| !SymLink  || Symbolic links ||
-|| Permissions || The permissions (not contents) of a POSIX path ||
-|| Action || Actions to be performed as part of a bundle installation ||
+.. include:: ../server/configurationentries.txt
 
 An example of each entity type is below.
 
 .. code-block:: xml
 
     <Package name='bcfg2'/>
-    <ConfigFile name='/etc/bcfg2.conf'/>
+    <Path name='/etc/bcfg2.conf'/>
     <Service name='ntpd'/>
-    <Directory name='/var/tmp'/>
-    <SymLink name='/dev/MAKEDEV'/>
-    <Permissions name='/etc/passwd'/>
     <Action name='action_name'/>
 
-Configuration Entity Name Attribute
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-With the exception of the Action Entity type, the value of the configuration entity name attribute is not arbitary.  It must map to entities of the same type in the Literal Configuration, which in turn map to physical entities on the client.
-
-For the most part the physical entity being mapped to is intuitive and are listed below.
-
-|| '' '''Tag''' '' || '' '''Description''' '' ||
-|| Package || name of the software package ||
-|| !ConfigFile || Full absolute path of the configuration file ||
-|| Service  || Name of the init script for the service which may not be that same as the name of the daemon started or the package name ||
-|| Directory || Full absolute path of the directories ||
-|| !SymLink  || Full absolute path of the symbolic linkss ||
-|| Permissions || Full absolute path of the file or directory ||
-|| Action || Arbitary name ||
-
 Writing Bundles
 ---------------
 
-Bundles consist of a set of configuration entities.  These entities are grouped together due to a configuration-time interdependency.  Basic services tend to be the simplest example of these.  They normally consist of
+Bundles consist of a set of configuration entities. These entities
+are grouped together due to a configuration-time interdependency.
+Basic services tend to be the simplest example of these. They normally
+consist of
 
 * some software package(s)
 * some configuration files
 * an indication that some service should be activated
 
-If any of these pieces are installed or updated, all should be rechecked and any associated services should be restarted.
+If any of these pieces are installed or updated, all should be rechecked
+and any associated services should be restarted.
 
 All files in the Bundles/ subdirectory of the repository are processed.
 Each bundle must be defined in its own file and the filename must be the
@@ -142,11 +147,22 @@ same as the bundle name with a .xml suffix.::
     atftp.xml
     ....
 
-Groups can be used inside of bundles to differentiate which entries particular clients will receive.  This is useful for the case where entries are named differently across systems; for example, one linux distro may have a package called openssh while another uses the name ssh.  Configuration entries nested inside of Group elements only apply to clients who are a member of those groups; multiply nested groups must all apply.
+Groups can be used inside of bundles to differentiate which entries
+particular clients will receive. This is useful for the case where
+entries are named differently across systems; for example, one linux
+distro may have a package called openssh while another uses the name ssh.
+Configuration entries nested inside of Group elements only apply to
+clients who are a member of those groups; multiply nested groups must
+all apply.
 
-Also, groups may be negated; entries included in such groups will only apply to clients who are not a member of said group.
+Also, groups may be negated; entries included in such groups will only
+apply to clients who are not a member of said group.
 
-When packages in a bundle are verified by the client toolset, the !ConfigFiles included in the same bundle are taken into consideration.  That is, a package will not fail verification from a bcfg2 perspective if the package verification only failed because of configuration files that are defined in the same bundle.
+When packages in a bundle are verified by the client toolset, the Paths
+included in the same bundle are taken into consideration.  That is,
+a package will not fail verification from a bcfg2 perspective if the
+package verification only failed because of configuration files that
+are defined in the same bundle.
 
 The following is an annotated copy of a bundle:
 
@@ -180,7 +196,15 @@ The following is an annotated copy of a bundle:
       </Group>
     </Bundle>
 
-In this bundle, most of the entries are common to all systems.  Clients in group "deb" get one extra package and service, while clients in group "rpm" get two extra packages and an extra service.  In addition, clients in group "fedora" and group "rpm" get one extra package entries, unless they are not in the fc4 group, in which case, they get an extra package.  Notice that this file doesn't describe which versions of these entries that clients should get, only that they should get them.  (Admittedly, this example is slightly contrived, but demonstrates how group entries can be used in bundles)
+In this bundle, most of the entries are common to all systems. Clients
+in group "deb" get one extra package and service, while clients in group
+"rpm" get two extra packages and an extra service. In addition, clients
+in group "fedora" and group "rpm" get one extra package entries, unless
+they are not in the fc4 group, in which case, they get an extra package.
+Notice that this file doesn't describe which versions of these entries
+that clients should get, only that they should get them. (Admittedly,
+this example is slightly contrived, but demonstrates how group entries
+can be used in bundles)
 
 || '' '''Group ''' '' || '' '''Entry ''' '' ||
 || all  || /etc/ssh/ssh_host_dsa_key  ||
@@ -211,12 +235,14 @@ The Bundle Tag has the following possible attributes:
 || origin || URL of master version (for common repo) || String ||
 || revision || Master version control revision || String ||
 
-As mentioned above the Configuration Entity Tags may only have the name attribute in Bundle definitions.
+As mentioned above the Configuration Entity Tags may only have the name
+attribute in Bundle definitions.
 
 Abstract Group Tag
 ^^^^^^^^^^^^^^^^^^
 
-In the Abstract Configuration plugins (Base and Bundle) the Group Tag may have the following attributes:
+In the Abstract Configuration plugins (Base and Bundle) the Group Tag
+may have the following attributes:
 
 || '' '''Name''' '' || '' '''Description''' '' || '' '''Values''' '' ||
 || name || Name of group. || String ||
@@ -260,32 +286,42 @@ configuration.::
         </Group>
     </Base>
 
-The format of the Base files are similar to those used by the Bundler.  The majority of the elements are usually Packages, but !ConfigFiles, Directories, Services, Permissions,  and !SymLinks may all be defined.  A partial example is below:
+The format of the Base files are similar to those used by the Bundler.
+The majority of the elements are usually Packages, but Paths of any type
+may all be defined. A partial example is below:
 
 Base Tag
 ^^^^^^^^
 
 The Base Tag has no attributes
 
-As mentioned above the Configuration Entity Tags contained in a Base definition may only have the name attribute in Base definitions.
+As mentioned above the Configuration Entity Tags contained in a Base
+definition may only have the name attribute in Base definitions.
 
 Abstract Group Tag
 ^^^^^^^^^^^^^^^^^^
 
-In the Abstract Configuration plugins (Base and Bundle) the Group Tag may have the following attributes:
+In the Abstract Configuration plugins (Base and Bundle) the Group Tag
+may have the following attributes:
 
 || '' '''Name''' '' || '' '''Description''' '' || '' '''Values''' '' ||
 || name || Name of group. || String ||
 || negate || Negate the group association (is not a member of) || (True|False*) ||
 
-An abstract group may contain any of the Configuration Entity types and other groups.
+An abstract group may contain any of the Configuration Entity types and
+other groups.
 
 Literal Configuration (Generators)
 ==================================
 
-A Generator is a bcfg2 piece of code that is run to generate the literal configuration for a host using a combination of the hosts metadata and abstract configuration.
+A Generator is a bcfg2 piece of code that is run to generate the literal
+configuration for a host using a combination of the hosts metadata and
+abstract configuration.
 
-A Generator can take care of a particular configuration element.  Any time this element is requested by the client, the server dynamically generates it either by crunching data and creating new information or by reading a file off of disk and passes it down to the client for installation.
+A Generator can take care of a particular configuration element. Any time
+this element is requested by the client, the server dynamically generates
+it either by crunching data and creating new information or by reading
+a file off of disk and passes it down to the client for installation.
 
 Usage of Groups in Generators
 -----------------------------
@@ -302,7 +338,8 @@ Nested groups are conjunctive (logical and).::
     if client is a member of group1 and group2 then
         assign to abstract config
 
-How the groups are configured is specific to the plugin, but here are two common methods:
+How the groups are configured is specific to the plugin, but here are
+two common methods:
 
 * xml configuration file (Pkgmgr, Rules)
 * file name encoding (Cfg, TCheetah, SSHBase)