logon script, so that we do not have to use stinky HTPP basic auth.

the interfaces table. This will be used to override the defaults that
newnode assigns using the node_types table, since for ElabinElab,
interface roles are actually picked however assign feels like it, not
according to any rules.

for the near future. Two big changes:

* Add WikiOnly accounts. An external user can register for an account on
  the wiki. Rather then use the registration stuff that comes with TWiki,
  redirect to new Emulab web page so we can manage all of the wiki accounts
  from one place. I modified the joinproject page to spit out a subset of
  the required fields so that its simple to get a wiki only account (just a
  few things to fill in).

  In keeping with current security practices, we still generate a
  verification email message to ensure the email address works. However,
  when the user completes the verification, the wiki account is created right
  away, rather then waiting for someone to approve it (since that would
  defeat the entire point of the wiki).

  Aside: I have not thought much about the conversion from a wiki-only
  account to a real account. That is going to happen, and it would be nice
  if that step did not require one of use to go in and hack the DB. Will
  cross that moat later.

  Aside: Rather beat up on the modify user info page too much, I continue
  to spit out the same form, but mark most of the fields as not required,
  and allow wiki-only people to not specify them.

* Both the joinproject and newproject pages sport a new WikiName field so
  that users can select their own WikiName. I added some JavaScript to
  both pages that generate a suitable wikiname from the FullName field, so
  that as soon as the user clicks out of the FullName, a default wikiname is
  inserted in the field.

  Both pages verify the wikinames by checking to make sure it is not
  already in use, and that it meets the WikiRules for WikiTopic names.
  (someone please shoot me if I continue to use WikiNotation).

wiki pages for projects and users on an existing testbed. This
assumes I can easily partition the actual twiki code into a
distribution that we can give people. I haven't really thought much
about that, but I assume its not too hard.

do not replicate the notes into 1200 files (and of course, so we
easily change the notes later).

Checked in so we can track their evolution and so you don't
have to rely on Mike to remember where he stashed them!

send the password hash over in the ssh, instead of getting it from the
local password file.

them. Also a few other helpful details and links.

Just noticed this was causing lots of "malformed interface record" logging.

I see this as a temporary hack until the permissions checks get fixed
in libdb to handle root.

script_wrapper.

	expwait [-t timeout] -e pid,eid state
	expwait [-t timeout] pid eid state
	where:
	     -e   - Project and Experiment ID
	     -t   - Maximum time to wait (in seconds).

(to tftpboot-elabinelab.tar.gz) so we can evolve it
separately without affecting the advertised tarball.

install.  This had been fixed for ops-install, but not boss.

that we can administer the inner emulab more convienently.

from info in the obstacles table.

is a tag for the box, and the draw flag says whether to draw the
obstacle as a rectangle. The intent is to move away from fixed
obstacles and labels in the jpeg files, and instead draw them
dynamically. Kinda simple to start with; lets see if we can represent
everything we need ...

Does it matter? No.
Should you care? No. (So why are you still reading this? :-)

I needed a place to quickly test the technique for obtaining the
disk size under Linux.  That will matter in frisbee...

The main change is that I now add an .htpasswd entry for the user's
emulab ID (stoller) in addition to the wikiname (LeighStoller). I also
create a mapping file (with perl dbmopen) to map from the Emulab ID to
the WikiName. This lets people log in using their Emulab ID, which is
pretty much required since we cannot pass the token to http basic auth
when it puts up the dialog box. Without this, we will forever be
answering questions from confused users.

TWiki already had something of a mapping mechanism, but it was broken
and horribly inefficient, so I ended up whacking the twiki code to
make it work with the above mentioned dbm file.

Wiki support is turned on in the defs file with a WIKISUPPORT=1 directive.

the .htpasswd file on ops. Note that I have disabled registration and
password changes from the twiki interface on ops for now. I'll think
about this as needed.

user does not change the windows password.

the rest of the code that ties it into emulab is still scattered around
my devel tree and under test.