Lots of cleanup for bcfg2-repo-validate rewrite:

* Changed all references to bcfg2-repo-validate in the documentation
  to bcfg2-lint
* Wrote man pages for bcfg2-lint and bcfg2-lint.conf
* Cleaned up straggling references to bcfg2-repo-validate in
  Makefiles, spec files, and the POSIX tool
* A few minor bug fixes

10 files changed, 17 insertions, 19 deletions

diff --git a/doc/appendix/guides/centos.txt b/doc/appendix/guides/centos.txt
index 119c3d2f8..dae11e5d4 100644
--- a/doc/appendix/guides/centos.txt
+++ b/doc/appendix/guides/centos.txt
@@ -244,7 +244,7 @@ file should look something like this
 
 .. note::
     When editing your xml files by hand, it is useful to occasionally run
-    `bcfg2-repo-validate` to ensure that your xml validates properly.
+    `bcfg2-lint` to ensure that your xml validates properly.
 
 The final thing we need is for the client to have the proper
 arch group membership. For this, we will make use of the
diff --git a/doc/appendix/guides/fedora.txt b/doc/appendix/guides/fedora.txt
index e8c1af7b6..db23e94bf 100644
--- a/doc/appendix/guides/fedora.txt
+++ b/doc/appendix/guides/fedora.txt
@@ -249,8 +249,7 @@ file should look something like this
 
 .. note::
     When editing your xml files by hand, it is useful to occasionally
-    run ``bcfg2-repo-validate`` to ensure that your xml validates
-    properly.
+    run ``bcfg2-lint`` to ensure that your xml validates properly.
 
 Add a probe
 +++++++++++
diff --git a/doc/appendix/guides/import-existing-ssh-keys.txt b/doc/appendix/guides/import-existing-ssh-keys.txt
index e606ba908..64a1b62cd 100644
--- a/doc/appendix/guides/import-existing-ssh-keys.txt
+++ b/doc/appendix/guides/import-existing-ssh-keys.txt
@@ -46,7 +46,7 @@ Validate your repository
 
 Validation can be performed using the following command::
 
-    bcfg2-repo-validate -v
+    bcfg2-lint
 
 Run the bcfg2 client
 ====================
diff --git a/doc/appendix/guides/ubuntu.txt b/doc/appendix/guides/ubuntu.txt
index 56480796d..ff87e7d97 100644
--- a/doc/appendix/guides/ubuntu.txt
+++ b/doc/appendix/guides/ubuntu.txt
@@ -202,7 +202,7 @@ something like this
 
 .. note::
     When editing your xml files by hand, it is useful to occasionally run
-    `bcfg2-repo-validate` to ensure that your xml validates properly.
+    `bcfg2-lint` to ensure that your xml validates properly.
 
 The last thing we need is for the client to have the proper
 arch group membership. For this, we will make use of the
diff --git a/doc/help/faq/general.txt b/doc/help/faq/general.txt
index f8ecc9854..ae53ca399 100644
--- a/doc/help/faq/general.txt
+++ b/doc/help/faq/general.txt
@@ -51,6 +51,6 @@ The bcfg2-server process logs to syslog facility LOG_DAEMON. The server produces
 **Is there a way to check if all repository XML files conform to schemas?**
 
 Bcfg2 comes with XML schemas describing all of the XML formats used in
-the server repository. A validation command ``bcfg2-repo-validate`` is
-included with the source distribution and all packages. Run it with
-the ``-v`` flag to see each file and the results if its validation.
+the server repository. A validation command ``bcfg2-lint`` is
+included with the source distribution and all packages. ``bcfg2-lint``
+can also performs lots of other checks for common mistakes.
diff --git a/doc/help/troubleshooting.txt b/doc/help/troubleshooting.txt
index e593db2f7..033b60706 100644
--- a/doc/help/troubleshooting.txt
+++ b/doc/help/troubleshooting.txt
@@ -38,9 +38,8 @@ Check if all repository XML files conform to schemas
 ====================================================
 
 Bcfg2 comes with XML schemas describing all of the XML formats used in
-the server repository. A validation command ``bcfg2-repo-validate`` is
-included with the source distribution and all packages. Run it with the
--v flag to see each file and the results if its validation.
+the server repository. A validation command ``bcfg2-lint`` is
+included with the source distribution and all packages.
 
 If the bcfg2 server is not reflecting recent changes, try restarting the bcfg2-server process
 =============================================================================================
diff --git a/doc/server/configurationentries.txt b/doc/server/configurationentries.txt
index 4ade2d414..1d278fa0a 100644
--- a/doc/server/configurationentries.txt
+++ b/doc/server/configurationentries.txt
@@ -50,9 +50,9 @@ plugin that handles the entry in the case of `Cfg`_, `TGenshi`_, or
 a device, directory, hardlink, symlink, etc), then you will specify both
 the *type* and any other necessary attributes in `Rules`_. 
 
-Running ``bcfg2-repo-validate`` will check your configuration
-specification for the presence of any mandatory attributes that are
-necessary for the Path type specified.
+Running ``bcfg2-lint`` will check your configuration specification for
+the presence of any mandatory attributes that are necessary for the
+Path type specified.
 
 .. note:: A tool for converting old POSIX entries is available in the
           Bcfg2 source directory at tools/posixunified.py
diff --git a/doc/server/plugins/connectors/properties.txt b/doc/server/plugins/connectors/properties.txt
index e82cfc570..1cbc4cf65 100644
--- a/doc/server/plugins/connectors/properties.txt
+++ b/doc/server/plugins/connectors/properties.txt
@@ -26,7 +26,7 @@ contain parsed XML data as the "data" attribute.
 
 The XML data in a property file is arbitrary, but a matching ``.xsd``
 file can be created to assign a schema to a property file, which will
-be checked when running ``bcfg2-repo-validate``.  For instance, given::
+be checked when running ``bcfg2-lint``.  For instance, given::
 
     Properties/dns-config.xml
     Properties/dns-config.xsd
diff --git a/doc/server/plugins/generators/packages.txt b/doc/server/plugins/generators/packages.txt
index f001f157e..90cd19de4 100644
--- a/doc/server/plugins/generators/packages.txt
+++ b/doc/server/plugins/generators/packages.txt
@@ -273,7 +273,7 @@ Validation
 ==========
 
 A schema for Packages/config.xml is included; config.xml can be validated
-using ``bcfg2-repo-validate``.
+using ``bcfg2-lint``.
 
 .. note:: The schema requires that elements be specified in the above order.
 
diff --git a/doc/server/plugins/grouping/metadata.txt b/doc/server/plugins/grouping/metadata.txt
index 1c915e2cf..43cc6a2d7 100644
--- a/doc/server/plugins/grouping/metadata.txt
+++ b/doc/server/plugins/grouping/metadata.txt
@@ -217,9 +217,9 @@ useful results:
     </Groups>
 
 Each of the included groups files has the same format. These files are
-properly validated by ``bcfg2-repo-validate``. This mechanism is
-useful for composing group definitions from multiple sources, or
-setting different permissions in an svn repository.
+properly validated by ``bcfg2-lint``. This mechanism is useful for
+composing group definitions from multiple sources, or setting
+different permissions in an svn repository.
 
 Probes
 ======