emulab-install, or from the current root password.

install script, but I pulled out to create an independent script).
This works on both freebsd and linux based MFSs. The intent is to do
all of the localization automcatically for site admins, so that they
can import new MFSs more easily. This is also used from the new
install code to bring in the initial MFSs and localize them.

Here is what we localize:

* The timezone is copied from boss:/etc/localtime to mfs:/etc. Ryan
  says the upcoming version of the linux MFS will actually use
  localtime. 

* Copy boss:/usr/testbed/etc/{emulab.pem,client.pem} to mfs:/etc/emulab. 
  The former is for TPM, the later for the ssl version of tmcc.

* Copy out boss root ssh keys (pub) to mfs:/root/.ssh/authorized_keys.
  In an ElabInElab we take care to combine with outer boss keys.

* Copy out the image ssh host keys. These are the keys that we put on
  every image to avoid the ssh host key change sillyness. See notes
  below on how these keys are initialized on an existing emulab. The
  keys are copied from boss:/usr/testbed/etc/image_hostkeys to
  mfs:/etc/ssh directory.
  
* Initialize the root and toor passwords from a new sitevar named
  images/root_password (which is the encryption hash, not plain
  text). See notes below on how this sitevar is initialized on an
  existing emulab.

About initializing the host keys and the root password hash ... I
added a new update script (27) that will go out to the current frisbee
MFS and mount it, grab the current keys and password hash, and put
them into place on boss. At the moment I only look for a FreeBSD
frisbee MFS, since not too many people are running the linux mfs, and
this was hard enough as it is!

For a new installation, a new install phase script will build the them
and install into /usr/testbed/etc/image_hostkeys. I have not dealt
with the password yet.

slicefix to trust what it finds in the MFS.

Minor changes to error handling.

This is not as general or as useful as you might think.
Right now it simply controls what device gets used as console when
customizing the MFSes. "sio" is the default. Other choices correspond
to pxeboot variants: sio2, vga, null. Choosing vga also sets the magic
VGAONLY setting in the frisbee MFS ensuring that any customized (via slicefix)
FreeBSD image doesn't try to use the serial port as console.

A real solution for choosing node consoles would not be per-testbed.
It would be per-node-type and per-node. Right now the console type is
selected in that fashion via a combination of the pxe_boot_path and
frisbee/admin MFS OSIDs. At some point we should make the console setting
explicit.

localization, so slicefix can fully localize images after frisbee is
done.

* Split up boss/ops/fs install into indvidual modules; generally, what
  was a toplevel phase in the original files is not a file. This
  allowed for better code/variable reuse. No longer monolithic, which
  makes it easy to test and rerun parts.

* Incorporate "update" into the install process. Certain phase file
  can be used in update mode, as when the IP/subnet/domain changes.

* Moved the MFS setup from rc.mkelab into the normal install process.
  Users no longer have to do this themselves. Good thing.

* installvars.pm is a new library that has the merged set of the
  zillion variables that were at the top of boss/fs/ops install.