the user may have visited the last page with http. If they did, send them
back through https

more liberal about which links don't need delays. Before, we were
putting delays on anything that wasn't 100Mbps.

The other change is that for delay nodes, we set virtual link
bandwidths by rounding up to the next fastest speed of interface,
instead of hardwiring 100Mbps. Similarly, we set the speed of
physical delay interfaces to the card's 'native' speed instead of
hardwiring 100Mbps.

These changes work for our nodes and links, but are still not totally
general. Really, what needs to happen is that assign needs to be the
one to insert delay nodes, because it's the only place where we really
know which interfaces of what speeds are available on which nodes.
But, that is a very big project, since both assign wrapper and assign
need to be changed.

of the same speed. This is obviously not right, but I think it's
better than the old hack, which was that we assume switch ports are
100Mbps.

Some stuff Chris is working on should remove the need for this hack
because we will start keeping track of the speeds of switch ports.

did this with a simple macro called OUTPUT() that does the check and
bails from the current function. This was as boring and tedious as
life gets, but we should be protected from stack smashing now.

Also fixed up a couple cases where we take data from the client;
make sure that the sscanf calls are bounded.

interactive shell is allowed or not - paperpag will just exit
silently if interactive shells are not allowed, but no command was
given on the command line.

This variable is now off to prevent interactive shells, but all the
interactive code is still in place, in case we ever have a reason to
want it.

into $CHECKLOGIN_STATUS

since I had Jonathon check them in prior to testing them.

Provides a simple interface to create an NS file, and then an
experiment, for use on PlanetLab.

Exit with positive value so that web interface reports error to
the user, not to us!

at Jay's request.

for various table/columns pairs. Used by php/perl libraries
to check data values to make sure they are valid. Note that
the intent is not to check whats valid to stick in the DB,
but what our conventions regard as valid (exampe: a uid is
2-8 chars, alphanumeric, starts with an alpha).

planetlab nodes.

privs in the default group.

on initial failure and just prior to lease expiration (~1 hr before).

two-way assign). Has been tested on 5-node linux and bsd expts. Still chatty,
still does not log. Also does not yet incorporate changes from discussion
today, namely running ns on ops.

of the CHECKEMAIL function as a result.

switching the menu when user switches between http and https (since
the secret cookie is not transferred in http, we have no way of
actually knowing the user is logged in from the browser). So, add
another cookie that is a crc32 hash of the real cookie, and trasnfer
that in http mode. A valid crc32 hash simply indicates that the user
is almost certainly logged in from the browser (but does not impart
any privs until we get the real cookie), while the absence of the
crc32 or a mismatch indicates that user is almost certainly *not*
logged in from the browser, and so we draw the usual "not logged in"
page.

the first node in the list. Useful for the linktest stuff, and the
sync server is harmless.

The idea is to give us hooks for grabbing experimenters' tarballs (and
RPMs) from locations other than files on ops. Mainly, to remove
another dependance on users having shells on ops.

tarfiles_setup supports fetching files from http and ftp URLs right
now, through wget. It places them into the experiment directory, so
that they'll go away when the experiment is terminated, and the rest
of the chain (ie. downloading to clients and os_setup's checks)
remains unchaged.  It is now tarfiles_setup's job to copy tarballs and
RPMs from the virt_nodes table to the nodes table for allocated nodes.
This way, it can translate URLs into the local filenames it
constructs. It get invoked from tbswap.

Does the actual fetching over on ops, running as the user, with
fetchtar.proxy.

Should be idempotent, so we should be able to give the user a button
to run webtarfiles_setup (none exists yet) yet to 'freshen' their
tarballs. (We'd also have to somehow let the experiment's nodes know
they need to re-fetch their tarballs.)

One funny side effect of this is that the separator in
virt_nodes.tarfiles is now ';' instead of ':' like nodes.tarballs,
since we can now put URLs in the former. Making these consistent is a
project for another day.