values to NULL.

	alter table nodes add destination_x float NOT NULL default '0';
	alter table nodes add destination_y float NOT NULL default '0';

Unlike other coords, these are meters and translated to pixels
later when displayed (trying to head in the right direction ...)

  looking for /proj/$pid/exp/$eid/rc.mkelab. This file constantly
  changes, so its convenient to just copy it over (since it is the
  script that drives inner emulab creation).

* No longer copy over rc.inelab; let it get installed when the inner
  boss/ops is created, from the testbed source tree that gets copied
  over.

longer comes from the project directory (really, my source directory
in the various projects). Instead, the source code comes from one of
two places:

* Using fetch on the inner ops and boss, make a special request to the
  outer webserver to return a tarball, currently stored in
  /usr/testbed/src, and created by toplevel makefile target "elabinelab".
  So, in your object tree (preferably one that is pure, without any of your
  own hacks) run "make elabinelab" and it will create the tarfile for you.
  The tarball is returned only to elabinelab experiments providing the
  experiment secret key (a variant of the existing spewrpmtar file stuff).

* Using the standard tarfile install command, albiet indrectly cause of how
  we hide all of the elabinelab NS goo. So, in your NS file you can do:

	tb-elab-in-elab 1
	set ::TBCOMPAT::elabinelab_source_tarfile \
			"/proj/testbed/tarfiles/emulab-src.tar.gz"

  Which will arrange for this tarfile to be installed in /usr/src, and then
  copied to the approriate place later when inner boss and inner ops are
  setup. The tarfile should be created in the top of your testbed source
  tree. This is given preference over method 1 above.

XXX Currently the tarfile is unpacked in /usr/src cause install-tarfile
does not create the target directory. As soon as we have new images, I'll
move this unpacking to a more suitable place.

this was never done ... I guess no one uses tarfiles much.

more checking of the config file and its contents.

the frames and robots; always put the contents of the wiggle_frame
back into the pool, otherwise, stale frames can hang around and cause
problems (duh); clear the wiggling flag after we receive the idle
status update.

gatech works.

the default one.

tree, sticking it into @prefix@/src/emulab-src.tar.gz. This is to make
it slightly easier for other people to mess with elabinelab since at
the moment all elabinelabs are running from my private source tree!

will be stored in /usr/testbed/src. The node requesting it has to be
part of an elabinelab experiment, and of course has to provide the
appropriate secret key.

Also make a check to see if a client has a newer version than us and
complain if so.  Indicates that an older tmcd got installed.

Change one of the proctitle calls to not use info that is not yet available.

been moved to jibe with what the vision system reports as their
position.

Drop the backup table I create when updating the permissions table so
that schema-scheck does not complain.

and off.

There are two different kinds of admission control checks, hence two
locations.

* From tbswap, easy checks are made (like, too many nodes of a real
  type), or trying to the use robot lab when its closed.

* From assign_wrapper.in. Because of virtual types, and because assign
  is the ultimate descision maker, we need to pass into assign per
  physical type limits, and let it deal with how virtual types map to
  physical types, and whether it exceeds the limits. So, when called
  from assign_wrapper, libadminctrl returns a hash of types and the
  counts the current experiment is limited to. That is put into the
  ptop file where assign deals with it.

If admission control goes sour, then just turn off the sitevar for it:
'swap/use_admission_control'

admission control is turned off.

before the exec to avoid holding open the mysqld socket in the new
process.

table, but also that there are any nodes of that type. The entry could
have been put into the table because of a set-type-limit line in the
ptop file.

previously, since it has more information

vision system bounds).