locking the "log" table (and hence preventing swap activity) for too
long.

from other experiments with the experiment in question... can't believe that
ever worked.  It's a testimony to how few people use that feature!

to get recreated correctly.  So have ports-install apply a patch (though
it doesn't automatically recreate the INDEX as that takes forever...)

dir resides, otherwise the package system get confused.

frisbee-loaded slice based on a tarball downloaded from boss.  For now,
the tarball is dynamically created by boss based on params sent to the
osconfig_dump.php script; it is populated with files and a MANIFEST based
on the files and constraints in the osconfig_* tables, which are pretty
self-explanatory.  Transport is not secure, nor intended to be -- nodes on
the control net or widearea nodes auth'd with a privkey can grab stuff
destined to them based on their IP addr.  For the MFS case, the tarball is
unpacked and the MANIFEST entries are executed/copied/extracted, and
(nearly all of) the client side is re-run.  For the slicefix case, we just
execute/copy/extract the MANIFEST entries in the mounted slice... there
are some useful env vars set for scripts to use.

If this mechanism ever becomes generally useful, or we're pushing big update
tarballs, we'll have to add a caching mechanism (doh).  Right now, it's just
for dongle-booted nodes or widearea nodes on which we cannot update the
physical boot media without much pain; as well as for making major whacks
to frisbee-loaded slices, which we need for the widearea case.

Also, call this from rc.cdboot (to update a "read-only" (real media is
mounted ro, but other parts of the fs are rw via unionfs or mfs) MFS),
and from slicefix.

NOTE: the client side osconfig script does not get installed from the
makefile; this is intentional.  This script should not be placed in our
local tftp'd MFSes, at least until there's some need for it!

special people).

special people).

We are NOT going to support this, I just want enough to get a 4.10 elabinelab
to swapin so that we can test upgrading the OS and packages.

security patchlevel (p3, aka the RELENG_6_3 branch).

but m2crypto-0.17 is always paired with python-2.5 in our ports so
we get away with it.  Hey, "it is what it is" man.

recorded in the emulab-{boss,ops} packages when I build them.

program protogeni/xmlrpc/client.py ... it is much easier to get a
simple python client running on your desktop then a perl client. Only
package you need to install is M2Crypto, which is easy. Perl needs
about 10 packages installed to xmlrpc over ssl. Sheesh.

an md buf so we can "write" anywhere -- including /usr/local/etc/emulab .
Token effort to not use unionfs on pre-6.3 fbsds, since unionfs is
only (more) stable from 6.3 onwards.  Also bumped the md allocations a
bunch.