Just noticed this was causing lots of "malformed interface record" logging.

I see this as a temporary hack until the permissions checks get fixed
in libdb to handle root.

script_wrapper.

	expwait [-t timeout] -e pid,eid state
	expwait [-t timeout] pid eid state
	where:
	     -e   - Project and Experiment ID
	     -t   - Maximum time to wait (in seconds).

(to tftpboot-elabinelab.tar.gz) so we can evolve it
separately without affecting the advertised tarball.

install.  This had been fixed for ops-install, but not boss.

that we can administer the inner emulab more convienently.

from info in the obstacles table.

is a tag for the box, and the draw flag says whether to draw the
obstacle as a rectangle. The intent is to move away from fixed
obstacles and labels in the jpeg files, and instead draw them
dynamically. Kinda simple to start with; lets see if we can represent
everything we need ...

Does it matter? No.
Should you care? No. (So why are you still reading this? :-)

I needed a place to quickly test the technique for obtaining the
disk size under Linux.  That will matter in frisbee...

The main change is that I now add an .htpasswd entry for the user's
emulab ID (stoller) in addition to the wikiname (LeighStoller). I also
create a mapping file (with perl dbmopen) to map from the Emulab ID to
the WikiName. This lets people log in using their Emulab ID, which is
pretty much required since we cannot pass the token to http basic auth
when it puts up the dialog box. Without this, we will forever be
answering questions from confused users.

TWiki already had something of a mapping mechanism, but it was broken
and horribly inefficient, so I ended up whacking the twiki code to
make it work with the above mentioned dbm file.

Wiki support is turned on in the defs file with a WIKISUPPORT=1 directive.

the .htpasswd file on ops. Note that I have disabled registration and
password changes from the twiki interface on ops for now. I'll think
about this as needed.

user does not change the windows password.

the rest of the code that ties it into emulab is still scattered around
my devel tree and under test.

Put iface arg first so that remaining arguments can be multiple mac addrs.
Send one packet per mac addr.

To enable WhOL, you need to add outlets table entries for nodes which are
whol-enabled.  The power_id encodes the interface on boss to use:

+---------+-----------+--------+----------------+
| node_id | power_id  | outlet | last_power     |
+---------+-----------+--------+----------------+
| pcwf6   | whol-fxp0 |      0 | 20050318152119 |
+---------+-----------+--------+----------------+

You then need interfaces and wires table entries for that interface on
boss, so that snmpit works with syntax like "boss:1".  This is probably not
really needed once the VLAN has been setup.

You need a magic VLAN called "WhOL", I used VLAN 999.  Add it to all the
switches and trunks.  Put boss's port in it.  It will remain there, enabled,
forever.

In the interfaces table entry for every interface that supports WhOL,
you need to set the 'whol' field to 1.

Used in the power_whol module.

Untested, but compiles!

Put back the changes I removed in my last commit.
You would think I would know how to read diff output by now...

I did the "back half" support.  If the 'mustwipe' field is non-zero
in the reserved table entry for a node then its disk must be zeroed.
How the zeroing is done, depends on the value of the mustwipe field.
Right now, '1' means pass the '-z' option to frisbee to have it zero
all non-allocated blocks.  The value '2' is reserved for enabling a
"full wipe" pass of the disk before running frisbee, which Keith Sklower
(DETER) wanted to be able to do.  Note that 1 and 2 are effectively the
same, if we are loading a full-disk image; i.e. all non-allocated blocks
from the new image are zeroed.  But if the disk were being loaded with
a single-partition image, then "frisbee -z" would only wipe unused
blocks in that partition.

The reload_daemon has been modified to extract the mustwipe info and
invoke os_load accordingly.   os_load now takes a "-z <type>" option
to enable the zeroing by setting a value in the current_reloads table.
tmcd will read and return that info to its caller in the "loadinfo" command.
Finally, the rc.frisbee script that runs in the frisbee MFS extracts the
loadinfo info and crafts the frisbee startup command.

What still needs to be done is the "front end," how the user specifies
the value and how it winds up in the DB reserved table.  This will probably
involve addition of state to the experiments table as this will likely be
a per-experiment setting.

Unified the 'dot' handling (status printing) of frisbee and imagezip.
They now both report the number of chunks remaining along with the dots.
Also put out a periodic splat for every GB of uncompressed data we write.
This is useful when you are zero-filling, since otherwise it appears that
frisbee has hung when it is really just zeroing the last unused 100GB of
your disk.