Cleaned up modules, separating implementations from the headers. Changed ugly g++ 3.* compatability hack into a robust support.

nodes, rather then hardwiring the speed/duplex in delaysetup. We
already started doing this for phys interfaces underlying veth
interfaces, but Mike requested we do this for delay nodes as well so
that we do not hardwire 100Mb into the script.

have a power outlet! At least we will know ...

happy.

differentiate clients.

* Put in debugging timestamps to figure out why so slow.

* Cleanup, fixing bad identing, bad style, bad comments, etc.

* Restructure so that instead of locking three tables (nodes,
  reserved, and node_activity), we just need to lock the reserved
  table, by moving the node existence check to before the main loop,
  and the node_activity update to after we unlock tables. Not locking
  the nodes table results in less serialization and less waiting for
  the lock to be granted.

* XXX: Check each node for an entry in tiplines table; Do not call
  into console_setup.in if none of the nodes have tiplines. This is
  not a very clean thing to do of course, but it saves up to half the
  time it takes to do an nalloc cause of the min startup time for our
  perl scripts (almost 1/2 a second). When allocating virtnodes on a
  physnode, no reason to even call console_setup.in.

Bottom line? Well, not as good as one would like ... time to allocate
10 vnodes on a pnode goes from .8 seconds to .4 seconds ...

which is a pc3000 (aka "wireless node") as configured for our cluster

time. Silly, silly, silly ...

Fixed code to come into compliance with g++ 3.*. More specifically, I removed header information which allowed the deprecated code to be used, and changed the deprecated code itself.

try to contact our boss

contains instructions other than just SQL to run.

Instructions for recovering the DB.

system and newclient

       that an experiment prefers to use modelnet for traffic shaping.
       At some future time maybe we can mix modelnet with delay nodes,
       but please do not hold your breath waiting.

	alter table experiments add usemodelnet tinyint(1) NOT NULL \
		default '0' after useprepass;

       Add modelnet_cores and modelnet_edges variables to hold user
       tunable number of physical core nodes and edge nodes to throw
       at a virtual topology.

	alter table experiments add modelnet_cores tinyint(4) unsigned \
		NOT NULL default '0' after usemodelnet;
        alter table experiments add modelnet_edges tinyint(4) unsigned \
		NOT NULL default '0' after modelnet_cores;

       Add ismodelnet and isphantom slots to node_types table. ismodelnet
       is set for modelnet nodes (which are also going to be isvirt).  Add
       isphantom to mark nodes that do no get underlying physical nodes;
       there will be an entry in the reserved table but no entries in the
       nodes table. Initially, modelnet virtual nodes will all be phantoms.
       Will possibly change later.

	alter table node_types add ismodelnet tinyint(1) NOT NULL \
		default '0' after isvirtnode;
	alter table node_types add isphantom tinyint(1) NOT NULL \
		default '0' after ismodelnet;

       Not sure that isphantom is going to work cause of the number of
       queries that join reserved with the nodes table. I might end up
       making nodes dynamic instead, creating and detroying them on the
       fly. I would prefer that isphantom works, but I am willing to live
       with isdynamic since we can use that for all of our virtual nodes.

	alter table node_types add isdynamic tinyint(1) NOT NULL \
		default '0' after isphantom;

zero bandwidth weren't getting printed out.

(FreeBSD 4 binary won't work under FBSD5 due to ioctl change)

the case that they didn't give us a hostname.  It just mocks up a
bogus hostname of dhcp-ip.wa.emulab.net and sends that along.
The substantive change is that it now prefers extracting the IP
address from the ifconfig for the interface instead of via hostname,
which is pretty unreliable.  But it'll try both.