GitLab

setup logs, just save them in the work directory. On error, they are
still emailed though.

Clean up a few files that shouldn't be checked in.

of adding copyrights to them.

<sklower@vangogh.CS.Berkeley.EDU> for the following, related to the -z (zero)
option in imageunzip/frisbee:

  1. For the case where a full-disk image is smaller than
     the disk the image is being unzipped onto, we added
     code to zero the area between the end of the image and
     the end of the disk.

  2. During the unzipping process, when zeros are being written
     at the end of a chunk, a write() that returned a length
     different from the expected value previously caused an
     infinite loop.  We noticed this problem at ISI, on a number
     of pc733s, which we suspect may have (relatively minor)
     hardware disk problems.

The latter addressed a Mike-o that has existed for 4 years.  Call it failure
resilient computing or just plain denial, but because of a botched conditional,
I was ignoring failed writes to the disk.  This lead to one of those infinite loop
thingees if you actually had a bad disk.

used remote sites still running ancient FreebSD 4.10.

than 35 program agents on the same node.

Reported by "Randy Robertson" <rmrobert@isi.edu>.

IO::Handle::opened method doesn't work when a ref to STDOUT/ERR are stored in
a variable since it really a glob in perl 5.005.  IN 5.8 it works for some
reason.  To fix use IO::Handle::opened($$this) not $$this->opened()

older perl for reasons that are beyond me. Change to good old swap and
go.

declared NOT NULL (not necessary in 5.0).

ElabInElab experiments, so as not to consume an interface.

I actually modified Keith's changes so that we can dynmaically choose
the single or dual model in the NS file (Keith's changes hardwired the
system to only single control network) since the single network model
has the disadvantage of not allowing new nodes to be added to an inner
elab, which would make it impossible to test some things (like the
newnode path!).

To choose the single control network model, place this in your NS file:

	tb-elabinelab-singlenet

other it defaults to the older dual network model.

bigger then a /24 network, as in Utah's network. Mostly the changes
are how we deal with the reverse zone file creation and what gets
stuck into the named.conf file. Prior to this commit, we assumed a
single /24 network, cause thats how it looks in an elabinelab
experiment (which is where its critical to have the named config files
generated automatically).

But with the changes to support a single control network, the named
setup inside elabinelab is bigger then a /24 and the reverse files
have to be created and populated correctly.