Import most FAQ items from old web site

Import most of the FAQ entries from our old web site.  A few outdated
questions have been omitted, many of the imported ones were updated in
one way or another, and the order of the development-related questions
has been changed.  Also, the phrasing of some questions has been
modified (just to make the headings shorter).

For the record, this is the original list of questions from the old web
site:

General
-------

* Who controls the Nagios Plugins project?
* What license is Nagios Plugins distributed under?
* Who owns the copyright for the Nagios Plugin code?
* Can I submit a patch to this project?
* Do you accept donations?

Compiling
---------

* ./configure appears to hang
* check_ldap, check_radius or check_pgsql don't compile even though
  configure output says the required libraries are present
* How come check_http/check_tcp doesn't work with --ssl?
* How do I compile the Nagios::Plugin perl module?
* I can't compile check_mysql on solaris
* I get '":types" is not exported by the Params::Validate module' when
  running tests
* Why does Solaris use pst3 for check_procs?

Installing
----------

* Some of the root plugins (check_dhcp and check_icmp) haven't been
  installed.  What's happening?
* Why aren't my plugins installed as the nagios user?  And what about
  root plugins?

Development
-----------

* How do I use Git?
* Can I add extra tests to the C routines?
* Can I use the Nagios Plugins in my own project?
* How can I find out more about writing a plugin?
* How do I make changes on nagiosmib?
* How do I prove the C routines work?
* How do I use and update Gnulib?
* How do I use the Nagios::Plugin perl module?
* How do the test parameters in NPTest.pm work?
* Private C APIs

1 files changed, 26 insertions, 0 deletions

diff --git a/web/input/doc/faq/extra-tests.md b/web/input/doc/faq/extra-tests.md
new file mode 100644
index 0000000..b508195
--- /dev/null
+++ b/web/input/doc/faq/extra-tests.md
@@ -0,0 +1,26 @@
+title: Testing C routines
+parent: FAQ
+---
+
+# Can I add extra tests to the C routines?
+
+The idea with the testing is to move as many functions as possible "lower
+down"; i.e., to the `lib/utils_*.c` files.  These functions can then be tested
+using the libtap routines in the `lib/tests/test_*.c` files.  It is easier to
+do unit testing here than to try and do higher level plugin testing, because
+you can fake data easier at this level.
+
+The routines available via [libtap][libtap] are equivalent to Perl's
+[Test::Simple][test-simple] ones.
+
+The libtap tests are separated out from the plugins ones (in `plugins/t`)
+because:
+
+1. They are testing the files in `lib/`, so should reside there.
+2. They require [compiling][compilation] to run.
+
+[libtap]: http://jc.ngo.org.uk/trac-bin/trac.cgi/wiki/LibTap "libtap"
+[test-simple]: http://search.cpan.org/dist/Test-Simple/lib/Test/Simple.pm "Test::Simple Module"
+[compilation]: doc/faq/compilation.html "Compilation"
+
+<!--% # vim:set filetype=markdown textwidth=78 joinspaces: # %-->