Useful for debugging.

Pain, oh the pain...

the UUID of the image gets you the most recent released version, but
you can use the UUID of a specific version.

the UUID of the image gets you the most recent released version, but
you can use the UUID of a specific version.

Conflicts:
	tbsetup/ptopgen.in

It appears that this was intentional and meant to denote a case
where the disk was not loaded. In Kevin's original code he set the
imageid to zero in this case. So we do the same (along with version=0).

We'll get this sorted out yet...

parent image when provenance is on.

Previously ptopgen was ignoring permissions granted to individual users
for OS access.  This commit also updates subos enumeration (previously
ptopgen was not looking at the permissions table at all for suboses).

From the comment:
     * "BOOTPART=" confuses the old rc.frisbee argument parsing
     * which looks for "PART=" with the RE ".*PART=" which will
     * match BOOTPART= instead. Thus an old script loading a
     * whole disk image (PART=0) winds up trying to load it in
     * partition 2 (BOOTPART=2). So we can pick one of two
     * versions, the one in effect when rc.frisbee changed its
     * argument parsing (v30, circa 6/28/2010) or the version
     * in effect when BOOTPART was added (v36, circa 6/13/2013).
     * We choose the latter.

Uses the new-ish imagezip -P option. But first we had to get that option
to imagezip. So the key-value interface between server and client now has
an IZOPTS key where you can pass options to imagezip (This is now used to
pass the -N that we have always specified as well).

Also changed imagezip to print out a less ambiguous message when the option
is in use, if will clearly say that it is full or delta. This matters because
we have to parse the imagezip output on the server to figure out what kind
of image it is!

All in the name of backward compat...

Otherwise we might run slicefix after a base image and before a delta
which could cause a train wreck in the FS if slicefix changes allocate
or deallocate blocks.

Also, grudgingly update some of the shell syntax to use constructs
introduced in the early 1990s. Sigh...this script will no longer run
on a PDP-11.

This check-in hits the web interface side of the node restrictions.
Users may not access the console or see the root password for nodes in a
restricted state (e.g. "blackbox" or "useronly").

A bit overdue, but here they are.

* Disallow image creation for any taint state on node/image
* Disallow console access for "blackbox" and "useronly" states
* Disallow node_admin for "blackbox" and "useronly" states

TB Admins are exempt from these restrictions.