to avoid hup-me-and-i-will-screw-ya mountd/NFS bug.

Use new -t option (use tmcd) in jails/plab

address of the interface instead of the dest&mask, which was bogus
anyway, and now wrong in the presence of variable netmasks for the
destination.

code (asking tmcd twice for routes, ifconfig, etc). Shashi will fix
later.

inside, but rather I do just enough to get the card booted (using
Abhijeet's minicom/expect scripts, but with changes to support the
configuration coming from tmcd. I also create a file of interface and
routeadd directives, so that the network configures properly, but
thats about it. Getting a more complete client side environment that
includes perl and sshd for the arm will have to wait.

Add a -V option to mkjail.pl telling it to use the virtual control net
IP (172.16.0.1) for the default route instead of the real control net
IP (155.101.132.1).  In this case, it also assigns a virtual control net
IP alias (172.17.<pnode>.0) to the physical interface so that the
aforementioned routes can actually be installed.

Add the same -V option (only valid with -j) in vnodesetup so that we
can get it through from bootvnodes.  (Also cleaned up the usage message
some)

The virtual control net address/mask are currently constants in mkjail.pl.
At some point they can/should be changed to config time options so that we
can easily use this on minibed too.

In theory, this (-V) shouldn't be an option and we should just use
virtual control net routing all the time.  But I want to get some more
testing and we have to resolve the minibed conflicts first.  So for now,
this is an option and it is off by default.

Haven't tied this option in with gated yet, so creating a vnode experiment
with Session routing still won't work.  If you want to do that, create the
experiment, watch gated blow up right and left, login to all the physical
nodes and change bootvnodes to add -V to the invocation of vnodesetup,
and then reboot everything.  Now it should be working!

per-jail software.

the project is different. This is not supposed to happen, but does
when reloading. Sigh.

iron out.  TMCD/libsetup now has a plabconfig commands that parallels
the jailconfig command.  The Plab boot process has been added to
libsetup and a -p option has been added to vnodesetup to parallel the
-j option.  Parts of the code that were Jail-specific, but labeled
just as vnode stuff have been renamed.  $vnodedir in vnodesetup has
been removed, since it was redunant with libsetup's CONFDIR, and
CONFDIR is much more intelligent.

* Parser: Added new tb command to set the name of the sync server:

	tb-set-sync-server <node>

  This initializes the sync_server slot of the experiment entry to the
  *vname* of the node that should run the sync server for that
  experiment. In other words, the sync server is per-experiment, runs
  on a node in the experiment, and the user gets to chose which node
  it runs on.

* tmcd and client side setup. Added new syncserver command which
  returns the name of the syncserver and whether the requesting node
  is the lucky one to run the daemon:

    SYNCSERVER SERVER='nodeG.syncserver.testbed.emulab.net' ISSERVER=1

  The name of the syncserver is written to /var/emulab/boot/syncserver
  on the nodes so that clients can easily figure out where the server
  is.

  Aside: The ready bits are now ignored (no DB accesses are made) for
  virtual nodes; they are forced to use the new sync server.

* New os/syncd directory containing the daemon and the client. The
  daemon is pretty simple. It waits for TCP (and UDP, although that
  path is not complete yet) connections, and reads in a little
  structure that gives the name of the "barrier" to wait for, and an
  optional count of clients in the group (this would be used by the
  "master" who initializes barriers for clients). The socket is saved
  (no reply is made, so the client is blocked) until the count reaches
  zero. Then all clients are released by writting back to the
  sockets, and the sockets are closed. Obviously, the number of
  clients is limited by the numbed of FDs (open sockets), hence the
  need for a UDP variant, but that will take more work.

  The client has a simple command line interface:

    usage: emulab-sync [options]
    -n <name>         Optional barrier name; must be less than 64 bytes long
    -d                Turn on debugging
    -s server         Specify a sync server to connect to
    -p portnum        Specify a port number to connect to
    -i count          Initialize named barrier to count waiters
    -u                Use UDP instead of TCP

    The client figures out the server by looking for the file created
    above by libsetup (/var/emulab/boot/syncserver). If you do not
    specify a barrier "name", it uses an internal default. Yes, the
    server can handle multiple barriers (differently named of course)
    at once (non-overlapping clients obviously).

    Clients can wait before a barrier in "initialized." The count on
    the barrier just goes negative until someone initializes the
    barrier using the -i option, which increments the count by the
    count. Therefore, the master does not have to arrange to get there
    "first." As an example, consider a master and one client:

	nodeA> /usr/local/etc/emulab/emulab-sync -n mybarrier
	nodeB> /usr/local/etc/emulab/emulab-sync -n mybarrier -i 1

    Node A waits until Node B initializes the barrier (gives it a
    count).  The count is the number of *waiters*, not including the
    master. The master is also blocked until all of the waiters have
    checked in.

    I have not made an provision for timeouts or crashed clients. Lets
    see how it goes.

Also a couple perf hacks:

* Local vnodes can start with the password/group file from the
  physnode, since locally they will be the same anyway. This avoids a
  blizzard of accounts requests at startup, which is by far the
  biggest chunk of data returned (well, except for host tables).

* To help serialize boot startup, vnodesetup now waits for the jail to
  finish starting up before it exits. It does this via a "goofy"
  mechanism I will not bother to describe.

the vnode on whose behalf they are operating. The library passes this
through to tmcd.

Move definition of the delay_mapping file in from liblocsetup so that
it is easily exportable withou another hoop.

Add configuration support for veth devices.

Change route and ifconfig generated script to do enable/disable
segments in the generated scripts so that per-jail configurations can
be added/removed easily by mkjail.

Add program agents configuration, with corresponding tmcd command to
return the list of program objects for a node (or jail).

Trafgens inside jails talk to the local elvind, not boss.

dotunnels, doroute, doiconfig all take an optional rtabid and pass
that through to libloc routines.

Add trivial support for getting the user shell from tmcd.

like we set hostnames of local nodes (v0.wa-jail-link.testbed.emulab.net).
Also build a proper /etc/hosts file just like local nodes inside the
jail. Minor change to dohostnames(); do not munge /etc/hosts in place!
Generate a new copy and then atomically move into place. Phew, this
was a close one! Mike has me really worried about race conditions now
that I screwed the pooch in the frisbee client.

Change paths for the vtun debug files to /var/emulab/logs.

(originally called for just the main address) so that all the routes
get installed properly.

the hosts files that we put on free nodes. For reserved nodes, we
start a new hosts file from scrath, and qualify localhost with
the domain found from the hostname command.

clients so they can create a proper .forward file. 2) Add some
test code for seeing how feasible it is to do accounts on ops/tips
using tmcd instead of direct ssh. Initial results are not good; too
many accounts; does not scale well. Going to need a smarter protocol
for doing hundreds of accounts, but I will leave this code in place
for now. Note, unlike testbed nodes, control nodes must connect with
ssl.

Add better timeout handling code to tmcc, which watches for progress
instead of just dumping after the timeout. This lets really slow
connections proceed okay, but still timeout out if nothing happens at
all.

This new tmcc has been installed into the sup trees for WIDE and RON.

bunch of jail changes. No matter, no one should be installing any of
this stuff to make a new image until I give the okay.

own script. It was just clutter in that library. Kill delay_update
since its not really used anymore, but give a delaysetup a -u option
to do that, just in case.

but eventually did not use it. Current images still make a call to it
from libsetup but will get an empty string that doesn't affect anything.

created by libsetup are now created in /var/emulab/boot; nothing is
written into /etc/emulab or /usr/local/etc/emulab anymore. This was
a requirement for jails, but is also a good thing to do anyway.
There are a number of jail config changes to support the old vnodes
and the new style jail vnodes; specifically, a setup routine to called
from inside the jail when it first boots up to the get the usual
assortmant of config info from tmcd. Also Merge local and remote
update routines into one. Other various little changes for SFS and the
MFS.

use perl dbm code.

destination was the same as hop. We don't need this since staticroutes
never puts such a route into the DB

  - Fixes the routing problem
  - A new type "sim" has been created but not in the DB. node_types and
    nodes remain unchanged. This will change after we figure out how
    to represent in the DB the local multiple virtnodes in one phynode case
    The frontend tb_compat.tcl adds the sim type and ptopgen associates
    a huge number of sim nodes to all local PCs.
  - All simulated nodes go into one pc untill I finish coding the distributed
    nse case. Also, sim nodes go through assign but with an explicit
    "fix-node" directive in the top file. A random free pc is chosen using
    the avail script in assign_wrapper. If we don't fix node it, assign
    maps sim nodes to multiple phy nodes even when a valid all to one
    mapping is possible.
  - Syntax for nse:

   $ns make-simulated {

       set simnode1 [$ns node]
       set simnode2 [$ns node]

   }
   ...

   The old syntax

   set nsenode [$ns nsenode]
   $nsenode make-simulated {
   }

   is deprecated

  - All 38 frontend tests in the testsuite pass

  - A new table v2pmap has been added to handle multiple virt nodes to
    one phy node mapping. This is used in "tmcc hostnames" currently.

  - The phy node that is picked to run nse is loaded with a custom image
    FBSD45-NSE . This can use the default FBSD kernel if there is a mechanism
    to run at 1000HZ, have options IPFIREWALL_FORWARD and PERFMON turned on.
    The image is in the 'testbed' group. Do not delete this image.

  - Static routes now adds routes for the case dst == nexthop. The routing
    graph would be disconnected otherwise and I need to traverse this in
    assign_wrapper for nse. On the client side, such a route is filtered out in
    libsetup.pm

  - sim nodes are also correctly visualized

jailed environments.
Fix up sfs stuff so that warnings and errors from sfskey do not
get printed out on the console.
Add a jailedsetup stub for testing with jails; work in progress.

rc.ifc uses it unconditionally so it needs to exist.

on the RON nodes and in the new widearea image.