I'd be all for banding together for generally noble or cool or
rewarding spare crunch projects. I personally am a sys admin/tools
developer/network architect type who happens to have his own build
lab of machines (which I use to build tools on multiple platforms).
This lab tends to collect idle machines from time to time, like when
a machine is reclaimed from a departing employee but before it's
reallocated. So: I'm looking for a way to easily incorporate the
idle, spare machines into a computational crunch pool. But I also
need to be able to remove any of them at any time. I haven't figured
out the best way to do this yet, but I'd like to have these machines
devoted to "spare cycle, distributed computing" projects. Any
architecture thoughts? Cool projects? I'm currently trying to get
the rc5 bovine/distributed.net client up and running...
Erik Kline
ISNTA, Hal Computer Systems