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.