just in case we need it.

as independent options (-m and -p).

fileserver - ie. fs.emulab.net . tmcd and exports_setup now use this
variable rather than a hard-coded node name.

group directories are now created in a different tree than the
the project directory so that they can be exported independently of
the project tree to the nodes in a group experiment. The tree is
routed at /groups on boss/users and on nodes.

1. mkgroup,rmgroup,mkproj - Minor changes to reflect new group
   directory location (/groups). We leave a symlink in the old spot to
   maintain compatability, and to reduce the number of different
   directories that a person needs to worry about. So, when a group is
   made, you get a real directory /groups/pid/gid, and a symlink
   /proj/pid/groups/gid that points to the former.

2. tmcd/tmcd.c - Minor change to add the additional group directory mount
   in the mounts command. Only done when pid!=gid for the experiment.

3. tmcd/libsetup.pm and friends - Minor changes to fix the fact that
   mkdir does not create subdirs along the way unless the -p option is
   specified. Needed to create the local directory for the mounts
   returned by tmcd for group dirs. Pushed them out to the sup trees,
   although 6.2 images older than the most recent one are not going to
   work right. No one is using those images though, and we should just
   flush the sup trees.

4. exports_setup.in - Ah, the crux of the issue. I really dislike NFS
   at this point. The original idea was to export a third set of
   directories to nodes that were part of a group experiment. Those
   nodes would get /groups/pid/gid exported, and /proj/pid read-only.
   Well, no such luck. On users, /groups and /proj are both really on
   /q, and the old restriction of mountd not allowing an IP to
   specified more than once on the right hand side for any FS, reared
   its ugly head again. As far as mountd is concerned, /q/groups and
   /q/proj are the same thing, and so it bombed when I tried to export
   them on different lines, since that meant an IP was repeated twice.
   So, I reworked exports_setup, and now for any node that is part of
   a group experiment, it gets this:

	/q/proj/pid /q/groups/pid/gid -maproot=root 155.101.132.26

   which at least allows the individual group dirs to be protected
   from each other, but does not allow /proj/pid to be exported read
   only. Sigh.

Requires a special config file for each control net configuration,
we currently support only the pc600 and pc850.  This could be fixed by
dynamically generating the config file based on the interface info returned
from the DB.  Simple perl hack for someone.

routertype field in the nodes table. For eventual use when Mike is
ready with gated stuff.

Modify the dohostnames stuff as per dicussion with Rob and
Mac. Instead semi-usless node-N names, set the name of the interface
to node-LinkName, where the linkname comes from the virt_lans table,
and is the name of the link/lan that interface is sitting on. This way
the user can actually figure out the interface when doing his routing
by assigning names to all links/lans in the NS file.

One major bogousity is that in order to maintain backwards
compatability, I've instituted a new hostnames commands (hostnamesV2).
We need a good way to deal with versioning!

did the lanlink change. assign_wrapper does not really need any
changes at all, but I dropped a comment in. The only real change is
needed in the client side to convert a floating point from tmcd, into
an int to give to ipfw. Rather cheesy too, given that Perl does not
have a real conversion function (int() truncates).

currently unused cause the switches are unhappy when the nodes reset
to 10Mbs. Not sure what is going on with that, so punt for now and
return to it later.

stuff. Use -p option to use UDP instead of TCP connection.

can set up his interface. Necessary for doing 10Mb links without
inserting delay nodes. Presently, no one mucks with duplex, so it will
always be full in the DB.

The DB will now hold Kbs.

than having node types in interface-specific configuration scripts, they
use control_interface so that this information is only stored in one
place.

Also added ifcfg-eth{1,3} scripts which are not used now, but make it easier
to handle differing control interfaces in the future.

of the world!

linked list has been set up, don't just return. Instead, set a return value
variable and GOTO the bottom of the function where the code to free this
list lives.

netdisk is handled properly, since it never does a 'tmcc reset'.

a lurking case where GID is null. Need to find that, but in the
meantime this will keep the tmcd happy.

there have been 260,000 connects (and 260,000 disconnects) to the
mysqld server. 240,000 of them were from the TMCD! I've changed the DB
code to keep the connection to the server open, and let the server
time it out. The client side code library code already deals with a
auto reconnect if the server goes away, so no reason to open/close
this connection for every single DB query. Besides, it might help
reduce the amount of time it takes to answer a single tmcd query, and
that would be a good thing.

interface for this node.

control interface for this node.

hold separate values for each of the two pipes. This allows us to
treat the links asymmetrically with respect to the delay node
configuration. Changes to tmcd to return the expanded info, and rework
(completely) delay_config to allow user to change the duplex
characteristics (just like before), or just simplex characteristics by
specifying the pipe number. By convention (I invented) pipe 0 is
traffic coming in on iface0. Of course, none of the front end stuff
has been changed, so the changing a single pipe does not cause
anything in virt_lans to be changed, so those changes will be lost at
swapout. Also get rid of all the ssh'ed pipe config stuff in
delay_config. Instead, add a client side script called update_delays
to /etc/testbed on the experiment nodes. After updating the delays
table, just ssh over and run that script, which calls the existing
code. Less distribution of knowledge.

commit.