type for Control interface wire, and you need to specify the 'port' as
well as 'card' on interfaces (the default is usually wrong).

redirection as indicated in the tmcd_redirect table of the DB, which
says what DB name to contact for each node. That table looks like
this, as of this writing:

    CREATE TABLE tmcd_redirect (
      node_id varchar(10) NOT NULL default '',
      dbname tinytext NOT NULL default '',
      PRIMARY KEY  (node_id)
    ) TYPE=MyISAM;

On error, fall back to the main DB.

../testbed/testsuite/tbtest -full run tbdb frontend testbed chris \
	"10 pc 16 shark"

it will then reserve 10 pcs and 16 sharks (or fail) and then run all the
tests using those nodes.  This doesn't quite work yet.  It's awaiting an
update of tmcc/tmcd to have nodes look at the other DB.

Also made it a little more forgiving about the test DB being left around.

updated.  This was breaking the testing stuff as some scripts were still
using the One True DB.

run do:

	../testbed/testsuite/tbtest run tbdb frontend

but you could also something like do:

	../testbed/testsuite/tbtest init tbdb
	../testbed/testsuite/tbtest test frontend
	# notice that sharkshelf test is broken.
	# make changes
	../testbed/testsuite/tbtest/single frontend sharkshelf
	# note still broken
	# make more changes
	../testbed/testsuite/tbtest/single frontend sharkshelf
	# note fixed.
	../testbed/testsuite/tbtest/finish

Also added a -leavedb command which can be used in conjunction with single
to debug individual tests.  It prevents the removal of the test DB upon
exit.

software.

Reset def_boot_osid after a node is freed. Stops it from looking for old special kernels that might not exist anymore.

Added testmode. Won't update the database for netdisking, and won't reboot nodes. Will update partitions table as if the change had already happened.

they are not yet installed from the top-level makefile, pending a decision on
the best way to install files outside the @prefix@ directory.

Added configure option '--with-rcdir', which defaults to /usr/local/etc/rc.d,
that specifies where to install these.

(respectively).  I.e.:

$TESTMODE = @TESTMODE@;
...
if ($TESTMODE) {
	...
}

will terminate properly through web interface.

will catch most problems.

with the testing stuff.

Experiment clearing no longer generates log files.  They are all collated
into clear.log instead.

When a test fails a snapshot of the test DB is stored in its directory.

(i.e., make sure all device reads are block aligned/sized)

Put some asserts in imageunzip to verify the same