experiment, and not count its pnodes or duration as if it was swapped
in! Thanks Kirk.

The actual fix is simple. The script to fix up the existing stats
records was a bear and took me all morning to get right! Even so, its
probably no perfect, but close enough. That script in the sql directory
and mentioned in doc/UPDATING.

tmcc creator query.

and use it in mkusercert.  I need this elsewhere.

Don't define it for frisbee.

(i.e., for FreeBSD5)

Comment out ORBIT.  Reality treatment for some others.

script to avoid vis-ing parents of subnodes (ie. to avoid vis-ing
the PC hosting an IXP.) However, this was preventing us from vis-ing
fixed nodes at all.

 . Bump the tmcd version to 21, since this induces an incompatibility.
 . Fix the $ anchored CREATOR= pattern in common/config/rc.misc that
   forced the version bump.

the embedded BIOS disk number in sector addresses.  So you still cannot
create an image on disk 0 and load it on disk 1.

My Emulab page when logged in.

No. Really.

reassigned to a new virtual node.  We do this for every vnode, both inside
and outside the jail.

option was given (as is when called from experiment page). This
restricts the nodes to just those in the experiment.

This interacts with ghosting mode (where other nodes on other floors
are shown). In the above case, should ghosting show all nodes on other
floors, or just nodes in the experiment on other floors? For now, it
does the latter, but it might useful to have a mode for the other
case?

   (Leigh's last change)
2. Collect up all the failed nodes and just send one mail message.

This way we know "who done it" so we can smack em around if they nfree
something they should not have.

being loaded is a user image.

"anchored" (^xxx$) then force it to be anchored by wrapping it.

query that maps the peer IP to a node in the DB). This was primarily
used as a safety to make sure that the node_types entry really did
match (in case the luser picked experimental addresses that conflicted
with real testbed addresses?), but not sure this test really
mattered. But, just to be safe, I changed it so that we check for a
matching IP and role='ctrl'.

by more then just plab code.

the plab code.

This checkin adds the necessary NS and client-side changes.

You get such a firewall by creating a firewall object and doing:

	$fw set-type ipfw2-vlan

In addition to the usual firewall setup, it sets the firewall node command
line to boot "/kernel.fw" which is an IPFW2-enabled kernel with a custom
bridge hack.

The client-side setup for firewalled nodes is easy: do nothing.

The client-side setup for the firewall is more involved, using vlan devices
and bridging and all sorts of geeky magic.

Note finally that I don't yet have a decent set of default rules for anything
other than a completely open firewall.  The rules might be slightly different
than for the "software" firewall since they are applied at layer2 (and we want
them just to be applied at layer2 and not multiple times)

Made a pass over tar file related things:

	* os/install-tarfile: Added support for bzip2 compressed files and
	fixed the '.tgz' regex (it detected '.tar.tgz' before).  Also
	binmode'd some file handles to squelch a warning on Redhat 9.

	* tbsetup/fetchtar.proxy.in: Added 'https' as a valid protocol for
	URLs and 'tar.bz2' as a valid extension.  Changed the wget call to
	do 'timestamping', which means it should only download files that
	have changed since the last download.

	* tbsetup/tarfiles_setup.in: More 'https' and '.tar.bz2' stuff.
	When downloading tarballs, copy the file name extension from the
	URL onto the local file name so 'install-tarfile' can figure out
	how to decompress it properly.

	* tbsetup/ns2ir/tb_compat.tcl.in: Added a bunch of checks to the
	tb-set-node-tarfiles function.

	* www/faq.html, www/tutorial/nscommands.html,
	www/tutorial/tutorial.html: Flesh out and clean up tarfile related
	documentation.  Also added anchors for the individual functions so
	you can link to them from other pages.

pub key, root password, etc. Currently just returning the pub key,
which I stuck into a site variable. I need this for inner elab so that
the standard image can be used; root ssh from inner boss will fail
unless the pub key is changed, and we certainly do not want to have to
create special images for inner elab nodes, unless we want to of
course.