marked as active instead of new.

Add another system experiment, hwcheckup for automated testing of
nodes that have failed during a swapin.

What I did was create node table entries for the three SPP nodes.
These are designated as local, shared nodes, reserved to a holding
experiment. This allowed me to use all of the existing shared node
pool support, albeit with a couple of tweaks in libvtop that I will
not bother to mention since they are hideous (another thing I need to
fix).

The virtual nodes that are created on the spp nodes are figments; they
will never be setup, booted or torn down. They exist simply as place
holders in the DB, in order hold the reserved bandwidth on the network
interfaces. In other words, you can create as many of these imaginary
spp nodes (in different slices if you like) as there are interfaces on
the spp node. Or you can create a single spp imaginary node with all
of the interfaces. You get the idea; its the reserved bandwidth that
drives the allocation.

There are also some minor spp specific changes in vnode_setup.in to
avoid trying to generalize things. I will return to this later as
needed.

See this wiki page for info and sample rspecs:

https://www.protogeni.net/trac/protogeni/wiki/SPPNodes

proper format (datetime, not int).

lan entrys with a "link" set. These are lans that point to another
lan, as happens when an emulated link points to the underlying vlan
entry. This is sorta annoying when you want to look up the emulated
link! So, new option to Lookup() to allow this, cause I cannot
remember why I did it originally, and do not want to beak anything.

This is a highly specialized (aka, useless) command line option I put in
just to get a sense of how common shared chunks between images are; to help
answer the question: could a frisbee server that serves multiple images take
advantage of this to significant effect?

Not ideal, there is a startup script which in turn invokes a run_capture
script.  The latter contains the actual capture lines.  The idea is that
the latter could be auto-generated someday from info passed via tmcd.  But
at the moment, it is manually maintained.

vnode reboot works by halting the current instance and then restarting it
again.  Previously, reboot would fail entirely if the halt step failed
due to a missing pid file (i.e., the vnode wasn't running).  Now we just
continue on with the restart phase if this happens.

manifest.

at least with FBSD 8.x (or maybe it is "geom"?), they became relative to the
slice.  So we attempt to automatically differentiate them by looking for slice
starts that are less than the DOS partition offset.  Such a slice would
indicate relative addressing.  Should probably add an explicit option to
set/unset absolute addressing in case the heuristic is wrong.

compatible.  One important part: the new versions get rid of the infamous
"advertising clause" which has been gone from BSD files for a long time...

to open().

no-regeneration problem.  This is the case that you change the defs
file, but a particular script is not mentioned in
configure.in. Personally, I hate that long list of filenames which is
never up to date, and we are always running into the problem of things
not getting regenerated.

Rewrite instructions for building the uClibc toolchain, and
change install location of source tarballs.

by this page: http://www.zytrax.com/books/dns/ch9/serial.html

It boots, but not all the startup scripts work right yet.