the UUID means the client can access the profile to view it (and
thus instantiate it).

Don't need lots of write buffers because we are saving to a fast MFS.
Don't need lots of chunk buffers because signature files are small.

Allow specifying zero to mean no limit.
Make sure we never allocate more chunkbufs than we need.

Implement idle ("lack of progress") timeout on the server.

Timeout work on the client-side too. Implement idle timeouts (not for
SSL connections yet), fixup handling of over-all timeout. In particular,
if we are reading from a pipe ('-') don't start timeout til we get some
input from the pipe.

Add option to put out progress dots on the client (cuz we are all about
dots in imagezip/frisbee).

Fixed the message(s) of:
You cannot augment 'TestBed::TestSuite::Experiment=HASH(0x187f420)' because it has no super method at /usr/local/lib/perl/5.14.2/Mouse/Meta/Class.pm line 429.

fix bit-rot to match current perl 5.14.2 and current cpan respository. Need to pull in more modules for xml-rpc ssl support.

We were not logging the upload daemon.
We were not rolling the log for the master server.

This is the replacement for create-image. Rather than puzzle out how to
maintain backward-compat syntax while allowing all the new features in
create-image, I just made a new script. When we don't care about backward
compat anymore, we can just rename the script.

Anyway, this script takes a lot more parameters (see the comment at the
top) allow creation of full or delta images and uploading via NFS or
frisbee. Since delta images require a signature file, there is new code
to handle downloading (and uploading) these files. And since their size
is measured in 10s of MB, possibly too big for the default MFS, there
is code to create a temporary new MFS to hold them. Currently that MFS
is 64MB which is big enough for our current generation of images (16GB FS)
and will work on the pc600/pc850s.

Still need to redo the boss-side of image creation (create_image, not
to be confused with create-image...yeah, I know).

Make sure .sha1 file has same owner as image file.
If image file doesn't exist, get rid of any dangling .sha1 file.

Resurrect: get the basic signature matching code working again.

Enhance: add -U option to have imagezip update (or create) the
signature file. Previously, the signature file was created off-line
on boss with the imagehash command (that would be Mike's "imagehash"
(/usr/testbed/bin/imagehash) and not Leigh's "imagehash"
(/usr/testbed/sbin/imagehash)). Creating it as we create the image
makes a lot of sense...except for how we do it. We actually read and
create the hashes as a separate pass before we re-read, compress, and
create the image--so we read the disk twice. [This is primarily because we
are mooching off of the existing hash checking code (-H option). Doing
this right will require re-writing The Big Loop which makes a single
pass through the data, simultaneously dealing with disk IO, allocated
ranges, and compression blocks all of which have different size/alignment
criteria. But I digress...] Anyway, reading the disk data twice sucks,
but at least it is on the client and not on boss. The take away is:
don't create your images on pc600s.

Note that -U will always create a signature file for the complete disk
or partition even when you are creating a delta image (i.e., when combined
with -H).

Enhance: add "-P <pct>" option, used with -H, which tells imagezip that if
a resulting delta image would be over <pct> percent the size (where size
is number of uncompressed sectors in the image) of a full image, then just
create a full image instead. So "-P 50" says if it would be over half the
size, "-P 200" says if it was over twice the size, etc. If you always want
a delta image to be produced, use -H without -P. If you always want a full
image, don't use -H.

This is part 2 of supporting images. Part 1 is the DB and user interface
changes that Leigh is working on. Part 3 is next up and involves modifying
the image creation MFS to download and use signatures along with the
new imagezip when creating images. Stay tuned.

Experiments expire, not profiles

names in different kernels.