This commit is intended to makes the license status of Emulab and
ProtoGENI source files more clear.  It replaces license symbols like
"EMULAB-COPYRIGHT" and "GENIPUBLIC-COPYRIGHT" with {{{ }}}-delimited
blocks that contain actual license statements.

This change was driven by the fact that today, most people acquire and
track Emulab and ProtoGENI sources via git.

Before the Emulab source code was kept in git, the Flux Research Group
at the University of Utah would roll distributions by making tar
files.  As part of that process, the Flux Group would replace the
license symbols in the source files with actual license statements.

When the Flux Group moved to git, people outside of the group started
to see the source files with the "unexpanded" symbols.  This meant
that people acquired source files without actual license statements in
them.  All the relevant files had Utah *copyright* statements in them,
but without the expanded *license* statements, the licensing status of
the source files was unclear.

This commit is intended to clear up that confusion.

Most Utah-copyrighted files in the Emulab source tree are distributed
under the terms of the Affero GNU General Public License, version 3
(AGPLv3).

Most Utah-copyrighted files related to ProtoGENI are distributed under
the terms of the GENI Public License, which is a BSD-like open-source
license.

Some Utah-copyrighted files in the Emulab source tree are distributed
under the terms of the GNU Lesser General Public License, version 2.1
(LGPL).

clientside requres it to be there. As noted in previous revision, the
full emulab build always includes the clientside subdir, but a
clientside build will not necessarily include the rest of Emulab.

lib subdir.

This reverts commit 0a3ccf1f.

lib subdir.

of adding copyrights to them.

* Add EventRegiser() function to wrap up event_register. Takes a host
  and a port number, and constructs the URL for the caller. Not really
  a big change of course.

* Change call to event_register(); Now connect on localhost:BOSSEVENTPORT.

return instead.

the tail file of course. Called from TBdbfork() in libdb, EventFork
resets the event handle so that the child does a reconnect. Note that
I do not disconnect in the child since I have no idea what that is
going to do to the parents connection to the elvind, as Elvin makes no
mention of what to do in the presence of a process that forks after
connecting to the event server. At the least, this avoids a bunch of
warnings and errors from vnodesetup!

on configured variables and libraries.

which registering with the event system twice from the same process
causes a core dump. EventSend use to register once per call, but now
it keeps the connection open between calls. It gets unregistered in an
END{} block.

the delivery of multiple notifications. So, instead of a single
notification, which could result in missed ones, we now maintain a
queue.

basically work like the libdb.pm functions of the same name (and in
fact much of the code was stolen from there.)

Provides a simple single function call to send events. Intended for
use in scripts whose primary purpose is _not_ to interface with the
event system, like power and node_reboot. If more control/efficiency
is required (for example, these functions reconnect to the event
system every time they're called) , it's better to use the C-like API.

Example call:
EventSendFatal(objtype   => "TBEXAMPLE",
               eventtype => $ARGV[0],
               host      => "*" );

broken. Also, it made me slightly uneasy that there was no way to
prevent swig from putting one of its generated files in sorce
directory. So, I've just checked in the two major files that get
generated by SWIG, so that the make rule that runs it never gets
invoked.

One of the reasons for doing this is that swig generates slightly
broken code when the -exportall (which does perl module exports
correctly) arugment is given. A very minor amount of manual tweaking
of the generated .pm file can fix this problem. So, the checked in
copy of event.pm has these tweaks applied.

As a result of all of this, exports work correctly in the event perl
module, so the hacky practice of putting your program in the event
namespace is no longer necessary.

This is accomplished with SWIG, so that we can basically just call the
C functions from perl, and avoid a parllel implementation. Some glue
code is required, particularly for callbacks, macros, and functions
that return data through arguments.

Currently lacks support for a few functions, but is functional enough
to re-write the example C programs.