some additional privs; allowed to view/edit node logs and histories of
all nodes, plus some others.

Inclues the TinyOS apps we used for data gathering, and the tools
we used to process data collected by the TinyOS apps.

All are modifications of standard TinyOS tools/apps. I've modified the
READMEs to explain the changes I made.

At this point, the actual DRE caclulations are not done, but I wanted
to get a snapshot into CVS.

port:card.

Call this every place (I think I got them all) a port list is used in
snmpit.

allows us to remove the tempfiles created by them.

- Crash recovery. Saving in memory information to disk during a crash
  Checking disk for previously stored checkpoint information on boot-up

- Read-only mounted checkpoints. Checkpoints #1, #2 and mounted are
  accessible as /dev/chk1, /dev/chk2 etc.

reasonable!

mysteriously dies.

too. This is done by prefixing the salt with "$1$".

return value, and the return value for die() is not as predictable as
you might think!

1. Redirect to outer emulab XMLRPC server when invoked from an inner
   emulab (as it is from the newnode web page). The XMLRPC server
   constructs the response using the interfaces and wires table
   entries for the nodes in the inner emulab.

2. Changes hardwired "experimental" and "control" strings to libdb
   defs (which are actually different strings, but since no one
   actually looks at that part of the switchmac return, the change is
   not going to bother anyone.

boss and ops, which I now set to .252 and .253 instead of .70 and .74.
This avoids conflict and confusion.

dhcpd.conf so that all trace is really gone.

so needed to resplit the install/control-install targets.

 - os_load will not attempt to load a non-imagable node, it will
   be skipped without error
 - nfree will respect imageable even with an entry in scheduled_reloads
 - reload_daemon will free any non-imageable nodes that happen to make
   it into reloadpending/reloading

and change the name of a function in snmpit_lib.pm that has also
changed.

and if the dhcpd config file needs special entries for those nodes.

created before trying to install.

restarted by HUP'ing the event scheduler.

files that are given to TinyOS.

As part of this, support changing the ID programmed into the mote.
The user can supply this on the command line, or they can supply it
in the DB (soon to be hooked in to NS files), or, if neither of
these is given, it defaults to the numeric part of the node's name.

This is neat - it could be the start of a more general framework,
in which we do things like modify uploaded TinyOS kernels to use
the frequency assigned to the experiment, or let users set parameters
for their TinyOS kernels in their NS fields.

source.