second argument so that you can pass ($pid,$gid) when showing a
group's experiments. But, it has a default value, so you don't have
to around around passing a superfluous second argument for showing
user or project experiments.

directory, symlink in /proj/<pid> .

nodes it can).

Change exit value; return -1 on fatal error, otherwise return the
number of nodes that could not be allocated. Combined with the -p
switch, assign_wrapper can easily determine that nalloc was able to
reserve a subset of the nodes.

Also fix up getopts() call, which had its arguments backwards! Good
thing we hardly pass switches to nalloc.

Also add constant for ROLE=gw.

take into the account the fact that it works now for 55xx series
switches.

"fullconfig" command to cycle through the list of existing commands
and spit out a section for each. Not all of them of course; just a
subset that makes sense. I did not that mounts are a bit of a problem
cause of the USESFS argument. Not sure what to do yet.

where they are okay.

  code that was in libsetup has moved into this library, and underwent a
  giant cleaning and pumping up. The interface from your typical perl
  script now looks like this:

  use libtmcc;

  if (tmcc(TMCCCMD_STATUS, "optional arguments", \@tmccresults) < 0) {
      warn("*** WARNING: Could not get status from server!\n");
      return -1;
  }
  foreach my $me (@tmccresults) {
	print "bite $me";
  }

  The arguments and results are optional values. There is a fourth optional
  value that is a hash of config options (basically converted to command
  line switches passed to tmcc). For example, to set the timeout on an
  individual call, pass a fourth argument like:

	("timeout" => 5)

  There is also a way to set global options so that all subsequent tmcc
  calls are affected:

	configtmcc("timeout", 5);

  I'll probably clean this up a bit to avoid the direct strings.

  The result list is a list of strings. Since we are trending away from
  using tmcc to transfer large amounts of data, I think this is okay.

* A new tmcc.pl which does little more than load libtmcc and use it.
  This will become the new tmcc, with the existing C version becoming a
  backend binary for it.

* All of the perl scripts in tmcd have been changed to use the new
  library. I left the few uses of tmcc in shell scripts alone since they
  were of the simple variety (mostly "state" command).

* And again, if you have read this far, you will learn why I bothered with
  all this. Well, the existing code was really bad and it was getting out
  of control. Sort of like a squid that was getting harder to control as
  its rotting tenticles slithered into more and more scripts. Anyway ...

  More important, my goal is to use the libtmcc library to add caching.  I
  have not worked out the details yet, but I am envisioning a configuration
  file, perhaps generated initially by tmcd, of all of the config
  values. If the library finds that file, it sucks the info out of the file
  instead of going to tmcd. Eventually, this config file would be generated
  as part of experiment swapping and stored in the DB, but thats a longer
  term project, and perhaps orthogonal (how we fill the cache is not as
  important as adding the ability to use a cache, right?).

  Note that certain operations (like "state" and "ready") are flagged by
  the library to always bypass the "cache".

switches have some really low MAC timeouts!

many links to slip by unnoticed.

change.

the DB, when doing main install.

Also updated sql/database-fill.sql while I was at it.

are doing their own firewalling can leave them open.

program, it only took a couple of hours.  Heavily tested: it didn't core dump
examining my 20GB FAT32 partition, ship it!

Actually, I did imagezip/imageunzip a FAT12 DOS floppy.  Since imagezip
files are a minimum of 1MB (the chunk size), it is probably not practical
for saving 1.4MB floppies :-)

Also, updated the man page.

Previously, if you accessed a phys node by its real IP address (155.101.132.N)
from inside a jail, it used the default route going to the router and back.
Now it will put it out directly on the control net.

The main reason for this is so that minibed vnodes can reach their boss and
ops nodes.  Vnodes in mini don't have a default route that works, so we needed
a way to get to boss/ops.

Note that gated will remove this route when it starts up.  Thus, vnodes will
revert to using the default route to get to the real control net.  On mainbed,
this will still work (hop through the router as before).  On mini, it won't
work at all.

Moral: don't use session routing and vnodes on mini.

appended to the hostname. For the gateway interface on IXP nodes.

from the interfaces table of the parent node. This coincides with
Rob's changes to stash the IP there, and arrange for it to go into
DNS.

Changes to "info" option

set properly.

batchstate on an experiment.

someday, but not today!

fixed fix before declaring the fix was fixed. Note that I haven't
tested this fix either.

"Piece of cake!" he says...
"15 minutes" he says...

Well, a day later, we can now deal with extended partition tables.
It was almost easy.  The offsets in an extended partition table are
relative to the location of that table...mostly.  The exception is if
an extended partition table contains an entry for another extended table.
Then the offset provided is relative to the *first* extended partition
table found, not the current one.

This was also complicated by the NTFS library code which needs to be
fed a device special file corresponding to the filesystem partition.
So if I am cruising alone creating a whole disk image using /dev/ad0
and I hit a partition containing an NTFS, I have to figure out the
BSD name for that particular partition: "hmm..I'm looking at partition 3?
That would be /dev/ad0s3".  Its easy for the first 4 partitions, but for
extended partitions, I had to figure out how BSD mapped those partitions
into device names.  Once I became aware of the DIOCGSLICEINFO ioctl, this
was easy as it gave back all the info needed.

Latest linktest parser with callbacks inside ns, new representation of links and examples of duplex and simplex netbed extensions.

for all nodes the user has permission to use (checks the
nodetypeXpid_permissions table).