On Apr 5, 2007, at 8:39 AM, Alexandre Pereira Nunes wrote:
> As (some of) you know, I got a few gumstixes about a year ago as
> part of
> a gumstix experimental compile farm project. In fact, the gumstix
> were very liberal as for how the clusters were to be assembled and
> functions were to be run on it.
> I'm not sure what happened with the other nodes (besides me, I think
> that there were 3 or 4 other volunteers), but my current status is
> the cluster is offline for months, in fact, it was never fully
> operational (I hand-configured one front-end gumstix as the server,
> made another one as a distcc helper, but the other stations never went
> online). By lack of time, and as a result of that system image getting
> outdated (newer gumstix started to ship with new, incompatible,
> buildroot releases), I decided to bring that offline.
> But that's not fun and a waste of the resources kindly supplied by
> So I'm here asking for your opinions about our choices.
> I have a friend which is on electronics field and he's asking me for
> making a enclosure case for the whole cluster. That inspired me to
> it online again, as a native compiling cluster (this time with full
> power). That's one idea.
A cluster with software-RAID-over-netblock-devices where the MMC card
on each board is exported to the network via netblock, then software
RAIDed in some clever way was kind of how I'd originally imagined the
thing, with a native toolchain on the shared volume, and distcc all
> But since time passed and things eventually change, I would ask if
> would be of some use for the folks here, or if there are any other
> of what can we do with a few online gumstixes. I'm thinking of
> forking a
> buildroot tree to get it to build cumstom images for the cluster, that
> would make it easier for getting the whole thing up-to-date.
Shouldn't need much change -- just maybe a top-level .defconfig and a
linux.config/uclibc.config/busybox.config to turn on/off the stuff