A little lint removal.

elabinelab

dhclient port

older images inside the elabinelab.

elvind was).

include support for gatewaying elvin notifications from older elvin
clients into new pubsub system.

moved down to the pubsub layer ... but in the meantime (while I think
about it), add a hack to the elvin gateway that flags notifications as
coming from the gateway, and use the internal order rather then
creaing another elvin ordering, which turns out to be a different
order (cause the elvin hash function over strings is less then
perfect, but what is).

Anyway, the elvin gateway works in both directions and I can boot old
images and have them work with the new pubsub based event scheduler.

elvin_hashtable, so we can traverse it in the same order when computing
hmacs.

added real types to pubsub.

traverse function prototype.

receive events from both, but pubsub will only process events for the
handle the mainloop is running on or when a notification is sent through
the other handle.  So, for now, just use threads here.

both are in there now via ifdefs (bleh).  Link the scheduler against the
threaded version of pubsub and add some asserts to ensure that's the
case.

The program-agent on ops seems to work with the scheduler now.

to do with the swig wrapper, I think. Not sure though, and I have to
take off for a few hours.

I commented out the client side stuff in the event directory though since
I initially trying to get boss running on the new system.