* Do not have linktest daemon connect to boss; have it connect to
  local node elvind like all other local agents. Remove the event
  generation code (linktest was sending a KILL event to all other
  linktest programs), and replace with a system() call to tevc, which
  sends the event through the scheduler and exits; this will avoid a
  zillion tcp connctions to boss from the linktest daemon.

* A couple of process group changes to linktest daemon; the daemon
  appeared to be killing itself off.

* Fix to run_linktest.pl; It was just hanging after it completed,
  cause its child ltevent process was still running. Changed to record
  child pid, and kill/close ltevent child before exiting.

from libsetup (ISDELAYNODE()).

1. The Linktest daemon, linktest.c, now listens for a KILL event. If received,
   the daemon will kill the linktest.pl child process and all of its subchildren.
2. The daemon also listens for SIGSTP events from the linktest.pl child, and
   will kill the linktest.pl process and its children if linktest.pl dies
   unexpectedly.
3. Locking has been implemented in linktest.c to ignore requests to start linktest
   while a current run is executing.
4. The controller script run_linktest.pl now includes the following new options:
   -t   allows the user to specify a timeout in seconds for Linktest.
   -v   prints out better feedback from the Linktest run as it proceeds.

Major remaining items are:
1. Avoid NFS mount hups
2. More testing, especially on vnodes

For example, a 56kbps == 56kb == 56k. Missing a 'b' caused it to make
the links 100Mb whereas ns2 supports not specifying the 'b'.

* Fix for dynamic vnodes (previous revision); I forgot to make
  equivalent changea to the code for widearea virtual nodes.

* Add modelnet support; [-m c,v] option to use from assign_wrapper
  specifies the number of modelnet-core and modelnet-edge nodes to
  place into the ptop file for local nodes. Assign will end up doing
  modelnet assignment based on the number of physical core/edge nodes
  the user specifies in the NS file.

interfaces still get a real speed (although this does not actually
matter to anything, lets be pedantic, shall we).

interfaces.

that it is clearly marked as not in use!

a legal value; when interfaces are not in use, set the speed to 0.

longer using cpuspeed.awk to get the 'exact' speed.

newclient to find it.

writefloppy code. The point of doing this was for headless nodes, like
the new wireless nodes - both scripts have similar needs in terms of
communicating with the user through beep codes.

Added a '-h' option for headless operation, in which we go into an
infinite loop with a beep code on an error.

Added a '-w' option to make it write the node ID picked by boss to
a floppy.

Added a '-t' option, useful for testing.

Grab the node's CPU speed directly, instead of using cpuspeed.awk -
we don't want to have to keep updating that in the newnode MFS.

At some point, I will probably add the ability to do DHCP to this
script, since that's another thing that could fail that we'd like to
have a beep code for headless nodes.

can view them.

so that user can select them (like jail/delay osname)

possible to:

	gmake client
	sudo gmake client-install

on a FBSD4, FBSD5, RHL7.3, and RHL9.0 client node.

There are still some dependencies that are not explicit and which would
prevent a build/install from working on a "clean" OS.  Two that I know of are:
you must install our version of the elvin libraries and you must install boost.

(early stages of getting Emulab software to build under FreeBSD 5)

- have pump/dhclient script record the DHCP'ed interface in
  /var/emulab/boot/control_interface

- change control_interface script to first check for that file
  and use the contents if it exists

Note that, as of this commit, we are still telling pump/dhclient which
interface to DHCP on (i.e., we still determine the control net interface
the old way to invoke pump/dhclient) so this commit is not that useful.

What still has to be done is to change the startup to invoke dhclient/pump
on all interfaces.  This turns out to be a royal, royal PITA.

Stay tuned...

of the database).

when doing modelnet. Sure wish we had a better way to do this!

vserver/pcplab). Rather then 10000s of fixed node entries in the DB,
create node entries on the fly as needed (assign_wrapper), and then
delete them when they are no longer used (nfree). When new nodes check
in, no longer create all those nodes table entries (utils/newnode.in
and tbsetup/plab/libplab.py.in).

I've added a new library: db/Node.pm which is something I started a
while back, and decided to commit, along with the support for creating
and deleting virtual nodes. CreateVnodes() creates a new set of nodes,
choosing non-conflicting names in the DB, and then immediately
reserves them to the pid/eid specified. DeleteVnodes takes a list of
vnodes and deletes them from nodes,reserved,etc. This library does a
few other things which I am going to be playing with, so you might
want to go read the comment at the top of the file. Feel free to speak
up. CreateVnodes() is from called assign_wrapper when a node type has
the "isdynamic" property. Otherwise does the existing avail/nalloc
stuff. DeleteVnodes() is called from nfree when the node type has the
isdynamic property.

I've added a script (sql/delvnodes.pl) to run after updating the DB
and software. All free pcvm and pcplab virtual nodes are deleted from
the DB; reserved ones will get deleted whenever their experiment ends.
I've noted all of this in doc/UPDATING, including setting the
isdynamic property on pcvm in the node_types table.

I've left tbsetup/plab/libplab.py.in to create a single pcplab node
for the management sliver (still called -20). We can worry about this
later.

All this for modelnet?

widearea node.

has NULL or "".

created, and which named_setup generates.