Move them to defs-default.

Allow for per-user defs files to use . defs-default in them. I do this
by temporarly changing the path when evaluating the defs file, adding
the directory where the defs file lives. So, you can do this in your
personal defs file, whic saves on a lot of typing!

	. defs-default
	TBOPSEMAIL=stoller@flux.utah.edu
	TBLOGSEMAIL=stoller@flux.utah.edu
	blah
	blah
	blah

I also changed all of the *local* defs file to use the above format.

tree gets installed. I've set it for our default defs, and for all
the *-emulab devel defs files.

configure.in.

cron daily, on the fs node (ops) as root. Uses lots of configure variables
so that it does the right thing in any installation, without any
customization.

One possible caveat regarding quotas: If FS_NODE != USERNODE, they don't
have a login on the fs machine. So checking their quota won't work unless
the rpc.rquotad(8) daemon is running on FS_NODE, which we currently don't
do.

In order to do this right, I had to add a new configure var,
FS_WITH_QUOTAS, that has a space separated list of file systems that have
quotas enabled. (Ie the default is 'FS_WITH_QUOTAS="/q /users"'.) It
doesn't have any default, since I couldn't come up with a reasonable one.
All the defs files have been updated appropriately to define this new
variable.

Before:
The main defs file (ie for configure) had an entry for WWWDEFS that
pointed to a <@WWWDEFS@>-defs.php3 file in the www/ directory. The www
defs file loaded some values about web pages, URLs, and some web
configuration parameters.

Problem:
Anything that was only in the www defs file was not accessible in the rest
of the universe (ie perl, C, and any other non-web-page scripts). For
instance, you couldn't have a perl script send an email to a user with a
link to the web site.

Solution:
Nuke all the www-defs files, move any important values into the main
configure, and change the web defs infrastructure to respect that. This
also meant adding about 3 lines each to all of the configure defs files.
(There really are about 10 new values you can change in your defs file,
but in almost all cases, the default values are the right thing.)

Upgrading:
External sites will need to move a few variables from their www-defs file
into their configure defs file. The example file should make it pretty
obvious. They may also want to customize some of the other vars that are
mentioned in configure.in and www/defs.php3.in .

picks it up from the main defs file via configure.

Fixed up everybody's defs and www defs files to match the new way of
doing things.

Add email aliases for testbed-stated and testbed-testsuite, and update all the defs files to use the same (or similar) addr for those lists as for testbed-logs. Make stated use the new alias too.

it is converted into a proper config.h file in the object directory.
Look for AC_DEFINE_UNQUOTED in configure.in. This removes some of the
headache of defining variables for C code in the makefiles. Be sure
sure to add -I.. to CFLAGS and include "config.h" in your source code.

fileserver - ie. fs.emulab.net . tmcd and exports_setup now use this
variable rather than a hard-coded node name.

things, although this solution is not hugely better ...

	BOSSNODE=boss.emulab.net
	USERNODE=users.emulab.net
	OURDOMAIN=emulab.net

(the new one is logs email address), move all those silly -with
areguments into a definitions file. See defs-defaults and
defs-stoller-emulab for examples. When you configure a development
tree, you want to create your own defs file, and then configure like
this:
	/src/testbed/configure  \
		--prefix=/usr/testbed/devel/stoller \
		--with-TBDEFS=/src/testbed/defs-stoller-emulab \
		--with-LEDA=/usr/testbed/LEDA/LEDA-4.0