Add a top level rules file with common stuff like install rules.
Beef up tbsetup makefile, and include above files. Add install of all
the tbsetup programs to the bin dir and to the bogus lib/tbsetup
directory.

project approval section.

current umask, and so I don't get the protection value I want.
Too lazy to go figure it out, and adding a chmod was easiest!

to run a setuid script, but in this case, we want to allow it. Actually,
I'm not entirely sure that this restriction makes sense in our semi
controlled environment, but better safe than sorry. If you think I'm being
too paranoid, let me know.

Program must exist in the testbed bin directory.

all the scripts send output.
Remove test for group writable directory (where program exists). Too
paranoid and too inconvenient for all of us since it would require root
installs all the time.

aren't set up correctly, and a few misc. cleanups.

and checks the database to make sure that the actual UID running the
script has admin privs (admin == 1 in the user table). Will also run
as root/tbroot without checks. Intended to be called out of the web
interface in the project approval code.

Cleaned up sanitization, added group ID sanitization, added some comments/placeholders for adding plastic

of the testbed, and what can be (or has been) done about them.

rearranged things so that only one chpass script is copied and sourced at the remote nodes rather than one per user

plastic