this field but forgot to removed it from the create file (it never
went into the migrate file).

interface_capability, which is a comma-separated list of speeds other
than the default which an interface supports.

our own. Also, leave the 'dhcpd_enable' option in rc.conf off so that
the old startup script will stay disabled.

Add wrapper script around dhcpd to restart it if it dies; whenever dhcpd dies, the testbed becomes unusable.

distributions; includes lock/delete statements to clear out existing
tables before filling them again.

Add db-fill-dist target to sql/GNUmakefile to use this new option.

Add target to utah/Makefile to call into the sql makefile and run the
db-fill-dist target. Be careful not to check this version in locally
of course.

to date if the check fails.

currently used.

node_types:isphantom which I added in 1.256 since I decided not to use
it; just use isdynamic instead. Add an isjailed slot to node_types
rather then hardwiring that fact to "pcvm" node type.

in table_regex.

touching a standard script

loopback interface (yeah, Linux will really do that...)

Also eliminate the non-REBOOT/BOUND/RENEW case up front to avoid excess
checking.

standard scripts.  The current FreeBSD 5 image uses this.

case that a delay (or all delays) are removed in a swapmod.

and php wrapper.

Add control- or shift-left-mouse for rotate as an alternative to middle-mouse to the usage message image.

linktest running at once (not a likely situation but ...). Also give
the window a meaningful title so that the browser does not stick in
the URL path.

buffering so that it will start to display output line by line.
1024 for Firefox, probably the same for Netscape. I hear that IE is
256 bytes.

so that the process ID is tracked in the DB and so that the user can
stop a linktest in progress from the web interface, even if its
started directly from experiment swapin.

* Changed the linktest web page to allow for killing a running
  linktest when called from the showexp page. Puts up a simple Click
  form, whose action is to call "linktest_control -k" which does the
  dirty work.

* Implement a simple frameset when running linktest. I did this cause
  it was something new and besides, it was more fun then trying to
  reverse engineer the modelnet model file. Anyway, when linktest is
  started, put up a new window that has a two window frameset. The
  right hand window is just the spew output from linktest as it runs
  (although with buffering not much turns up at first). The left side
  window has a single click box to stop the running linktest, whose
  action is to call linktest_control -k as above. By the magic of
  javascript, when the linktest finishes, the stop button is removed
  and replaced with a "Linktest Finished" message. So exciting.

in the DB, change that to Stop Linktest instead.