autologin of the swap-in user, and a user sshd on port 2222.

elvind/libelvin

       column in the reserved table and not the nodes table:

Also fix a cut/paste error and renumbed some items, we went from 1.279 to
1.270 and started counting up again.

made me look bad in front everyone. I really hate it when that
happens.

and the special multicast addresses.

exist; fire up frisbeelauncher early to see if it can get the image.
This is harmless in that frisbeelauncher can be called multiple times
anyway, so when its called is not really a big deal.

download images from the outer emulab. This script is invoked from
frisbeelauncher when ELABINELAB=1 and the filename does not exist
(thus attempting to get the image file before bailing). The
frisbeeimage script uses a new method in the RPC server to fire up a
frisbeed (using frisbeelauncher on the outer Emulab), subject to the
usual permission checks against creator of the elabinelab experiment
(I assume that the creator will have access to any outer images that
are used inside the inner emulab). If outer frisbeelauncher succeeds,
its return value is the load_address (IP:port), which is used to fire
up a frisbee client to get the image file and write it out (using
Mike's new -N option that just dumps the raw data to file). Once the
image is downloaded, control returns to inner frisbeelauncher and
proceeds as normal.

I whacked this together pretty quickly. Under heavy usage it might hit
a race condition or two, but I do not expect that to happen in an
inner elab for a while.

(like stated).

getting images for ElabinElab.

- add some missing casts
- avoid void * arithmetic
- change "q" printf formats to "ll"

Still not there yet by any means.  Note that the version of the NTFS library
we use won't compile with "-pedantic -ansi" so those are not part of the
default CFLAGS.

configure so that we can localize it for inner emulab. Not good to
overlap the address space between inner and outer emulab if inner
boss is going to use frisbee client to suck images from outer frisbeed.

This patch file is part of the RHL90 image build procedure.  It probably
doesn't belong here in the `doc' tree: it belongs *somewhere*, but nobody seems
to know where exactly.  Until a better place is found, here 'tis, alongside the
build script.

Minor improvement to the node.available() method so you can get the
number of free nodes of a particular type (e.g. pc850).

  * xmlrpc/GNUmakefile.in: Add node_avail symlink.

  * xmlrpc/emulabserver.in: Add some optional parameters to
    node.available() so you can specify the class/type of nodes as
    well as project credentials.

  * xmlrpc/script_wrapper.py.in: Add node_avail class that calls
    node.available() with the given parameters.

to the list of ALLOWED_PATHS.

This is a copy of `doc/updating-RHL.txt' r1.2, modified on Nov 12 2003.

I'm committing it now, before I start trying to clean it up.

This change makes the configuration more portable between testbed sites.

* sslxmlrpc_server.py: A rather gross hack that needs more thought;
  pass the client IP address to the emulabserver class instantiation,
  which is passed along to the new elabinelab module ...

* emulabserver.py: A new class called elabinelab which exports some methods
  that are to be used by an inner elab. At present, the IP address of the
  client is passed along and a bunch of checks are made that restrict the
  client to the inner emulab boss node, with the credentials of the
  creator of the inner emulab. In other words, the ssl certificate of the
  elabinelab creator is placed on the inner boss, and all proxy
  operations are invoked with this certificate (as the creator) and
  only from the inner boss node.

  The elabinelab class currently exports two methods; a power method
  to power cycle an inner node; the command is handed of the power
  command, which does the permission checks. Of course, the inner boss
  does its permission checks, but ultimately, the outer boss will
  allow the power cycle only if the client is allowed to power cycle the
  node.

  The other method exported is a vlans command to setup and destroy a
  set of vlans for an inner experiment. Permissions checks are modeled as
  above, with everything passed out to new snmpit.proxy script, which
  then invokes plain snmpit.

Log `auth.info' messages (`ssh' logins) to `users.emulab.net'.

This is done because we replace ceratin user- and group-management programs
(from the `shadow_utils' package) with versions that accept uppercase letters
in user and group names.  The Linux-standard (?) versions of those utilities do
not understand the CREATE_HOME option in the `/etc/login/defs' file.  In fact,
the standard `useradd' program goes out of its way to *complain* about the
option when it is found.  The relevant source comment from `src/useradd.c':

		/*
		 * RedHat added the CREATE_HOME option in login.defs in their
		 * version of shadow-utils (which makes -m the default, with
		 * new -M option to turn it off). Unfortunately, this
		 * changes the way useradd works (it can be run by scripts
		 * expecting some standard behaviour), compared to other
		 * Unices and other Linux distributions, and also adds a lot
		 * of confusion :-(.
		 * So we now recognize CREATE_HOME and give a warning here
		 * (better than "configuration error ... notify administrator"
		 * errors in every program that reads /etc/login.defs). -MM
		 */

Rather than suffer obnoxious warnings at boot time, we just avoid the option.

(2) building the patched, Emulab-specific kernels from source, and (3) cleaning
up the `lilo.conf' file itself after the kernel building and installation
process.

testbed programs rely on libraries found in `/usr/local/lib'.

hack to deal with inner vs outer control network.

except that it's been modified to the point of making the serial console usable
in the University of Utah Emulab.

The exact contents of this file vary according to the installation environment
in any case.

although the exact contents of this file vary according to the RPMs that are
installed when the system is created.