Mostly for debugging.

permission to the image being requested. Added for image backed
datasets. The key to this commit is being able to abort the logging and
return STDOUT/STDERR to apache so that the image can be streamed.
There is a corresponding change on the caller side, that adds a new
method CallMethodStream() that takes a file descriptor to send the
data to.

that it can be reused as for dataset snapshots. This was one of the
reasons that imaging progress modal was not slightly messed up for
datasets.

allocating so we can change the state in the display.

The metadata does not have anything sensitive, and this is easier than
rolling it into the secure download path via the CM.

its an admin page.

are marked global. Dataset download is otherwise handled via the
CM with credentials.

convert control chars for display.

wanting to call setgroups cause it is so slow. also refactor the code to
chown/chgrp user dot files so we can call it from reactivate.

Refactor the code that bumps user/project activity and calls exports
setup so that we can call it from reactivate.

When deleting a ZFS home/proj directory, do the ZFS rename and then
set the mountpoint=none, no need to have it mounted.

Guess we don't get any guests these days. Or they they don't whine, they
just go to Amazon.

portal brand. This closes issue #137.

See Mike thrash. Thrash Mike, thrash!

Another day, another weed patch...

Somehow I wound up out in these weeds... Tracking the drift has apparently
never been done in Ubuntu14.

Tweak button colors in genilib editor.

requested expiration, no need to do anything, including the permission
checks.

What I thought was the LCD for all OSes, /etc/ntp.drift, doesn't work
because ntpd does not run as root and it wants to create a tmp file for
the new drift value in the same dir as the driftfile.

So if /var/lib/ntp exists in the image, we modify /etc/ntp.conf to put
the driftfile there. The ntpstart and watchdog scripts should pick this
up just fine as is.

(ntpd is really dumb, and attempts to create its temp drift file as
$DRIFTFILE.tmp only.  Obviously we can't give ntp group-write into /etc.)

sfdisk no longer accepts any other unit than sector.  Ha, ha.

Also, warn user if they try to mkextrafs on an unpartitioned disk and
fail to supply '-s 1'.  We only generate partition 1, full disk size
(minus sectors 0-2048) in this case.

screen shots for the manual. This removes various bits of per-user info
from the display.

	https://www.cloudlab.us/login.php?cleanmode=1

While I was in there, I added adminmode so we can log in as admins when
the web interface is disabled.

(AFAIK, nothing has changed about dhclient, etc... I just noticed on the
Emulab d820s (which have BCM5720s, tg3 driver), the driver takes
anywhere from 7-9 seconds to simply init the card and autoneg with the
switch (I've seen worse times, too, i.e. 19 and 29 seconds!).)

dhclient is happy to start sending requests on interfaces that have no
carrier (gee, did it ever seem like a good idea to make that behavior
optional???).  Thus, if we get stuck with a control net NIC that has a
horribly long init/autoneg time, dhclient is far into its backoff
strategy on the control net, when it doesn't need to be!  In addition to
slow media negotiation, there are STP auto things that can further delay
the forwarding state of a switch port (like the ProCurve "auto-edge"
port setting that causes the switch to wait 3 seconds after media
negotiation for a BPDU).  So we have to be a little smarter about
bringing up the control net via DHCP.

So to combat these possible scenarios, we try two main things.

First, we modify findcnet to wait for one of two things to be true
before we start dhclient at all (or until a 6-second timeout is
reached): 1) if we have a previous control net device in
/var/lib/dhcp/dhclient.leases, we wait for that to come up; or 2) if we
don't have a previous control net device (i.e. first boot of an image),
we wait for at least one device to obtain carrier.  We could increase
the 6-second timeout, but we'll wait on that for now; this should be
good for now.

Second, we set initial-delay and initial-interval both to 3 seconds in
dhclient.conf ; hopefully this will give STP protection schemes a chance
to have gotten things straight by the time dhclient makes its first
retransmit.

I tried adding a forced 'ifconfig <X> up' to the udev interface handler
script, just to try to kick the device into autoneg mode ASAP, but of
course that didn't help anything.

I cannot improve on this unless we move to a split, managed dhclient
scheme, where we actually run a dhclient for each interface, and control
the backoff time much more tightly.  For now, I don't want to do either
of these things.