client software to widearea nodes. Most of these changes were to
reduce the embarrassment factor. At some point we need a proper
autoconf and such, but for now there is a makefile in the src dir for
creating the distribution.

I've tested it on a local linux node and mostly on a freebsd node, but
I've moved things around and so updating the RON nodes will require
some hand intervention by me at some point.

* Add ability to control timeout when invoking tmcc, and whether to
  fatally die if tmcc fails. Related change was to allow more options
  to be passed into tmcc by way of an additional options argument.

* Change to pubkey handling. tmcd now returns a list of pubkeys for
  each login. The entire list is written to the authkeys files, and
  the old is backed up (with mod time preserved).

* tmcd now returns a serial number for each use to indicate when
  user info has changed (via the web pages). Only users with updated
  serial numbers get modified (and new authkeys file created). This
  should vastly reduce the passwd/authkeys churning on the ron nodes,
  which periodically check for account updates. The little db file now
  records the serial number too.

* Change to os_usermod; Change the actual password string! Was not
  doing that before.

* Conditionalize all the tmcc.foo stuff that Shashi added; don't want
  any of this on remote nodes yet.

* Remove a bunch of printfs to reduce output clutter.

files are generated.

with cvsup.

in /etc/testbed for use by NSE

if it fails, we exit gracefully from the node setup instead of
screwing stuff up even worse. Basically, I converted all close($TM) to
CLOSETMCC($TM) which does the proper checks and dies if error.
This is probably not ideal either, but not really sure what the ideal
solution is when tmcc fails.

for a node, we start up NSE, even if no FullTcp traffic generators
are configured for the node

1) Merge in the accounts code that I did for ron. Instead of resetting
   the password file on each reboot, look at the node status to
   determine if the password/group file should be reset. If the
   node is free, reset it. Otherwise, we track changes to the password
   and group file now, so that users can change it and not have their
   changes wiped out at each reboot. I had to do this for the ron
   nodes so that the testbed software would not alter or delete
   already existing accounts; I keep a couple of little dbm files
   listing all the accounts/groups added. The only downside right now
   is if a node is reallocated before it is wiped clean; I plan to add
   an os_teardown phase to experiment termination asap.

2) Add tunnels support. New DB table (tunnels) provides information
   for running vtund to link up to remote nodes. Creates a vtund.conf
   file on the fly, and fires them off. The complication is that you
   cannot do the ifconfigs or the routes until the tunnels are
   connected, so that stuff has to be configured within the vtund.conf
   file on a per tunnel basis. vtund.conf has some sections for
   running commands when tunnels are brought up or down.

3) Damage the routing configuration code that Mike did. To support
   tunnels, as noted above, rc,route is no longer a simple list of
   commands, but a program that adds/dels routes based on the netmask,
   with a special "enable" section for the other stuff. This allows me
   to call it from vtund.conf for up/down on each tunnel'ed
   interfaces, as needed. Quite gross, but no way around it.

4) For remote nodes, add a vnodesetup script, invoked from boss when
   experiments are setup/torndown. This gets the tunnel/route/trafgen
   configuration and runs them. It then goes into the background
   waiting for a death signal, at which time it brings them down and
   cleans out the vnode state.

Removed rc.route script which is now generated automatically by libsetup
doroutingconfig code.

Random: removed some unused variables from freebsd/liblocsetup
(IFACE, CTLIFACENUM, CTLIFACE) which collectively hardwired the control net,
probably haven't been used in a while.

file in /etc/testbed, and if there such a file, take a different path
through the setup code that is a lot shorter (mounts, accounts,
startupcmd).  All the other stuff is bypassed. There are no
differences though between what you install on the MFS and what you
install on a regular node.  Just run the mfs-install target instead,
which creates the little ismfs file for you.

addr/port.

currently installed tmcd. The version number is passed through on
every tmcc request.

Telnet sources)

For now redirect of stdout/stderr to a file for diagnostic purposes.

This is for Shashi and NSE support. TMCD returns this new field in
the trafgens command, and libsetup.pm has a new test; do nothing if
the generator does not equal TG. This is a temporary change; finalize
when Shashi is done.

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.

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!

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.

a "cleaner" separation of the OS independent and OS dependent parts.
Lots of stuff moved to common libsetup.pm, shared by linux and
freebsd. OS dependent stuff is in liblocsetup.pm in the subdirs.
Other major change was to add "update" ability so that mounts and
accounts can be updated on the fly, when directed to do so from boss.
This is in support of shared experiments, so that as projects are
added to the share list, the mounts and accounts can be updated
without having to reboot.