[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Washi

On Sat, Nov 24, 2007 at 01:02:05PM -0500, Mark Duckworth wrote:
> Stephen R Marenka wrote:
> >On Fri, Nov 23, 2007 at 11:56:06PM -0500, Mark Duckworth wrote:

> >>Out of curiosity, how strapped are you guys for buildd's?  Can you 
> >>handle the loss or does this really screw you?  I may be able to setup 4 
> >>dual xeon aranym buildd's.  I just need the real falcon for myself.
> >>    
> >
> >I'd say we're hurting pretty badly overall. hobbes and garkin, our other 
> >two falcons, are both still down. a4000t seems to be gone for good. q650
> >doesn't seem to be buildding any more. Attrition is getting to us.
> >Further, we could probably use a box running experimental and security
> >was willing to support us for etch if we could run against a different
> >w-b. (I'm starting to think patching buildd to handle different wb
> >hosts would be the way to go there.)

> Not the news I wanted to hear.  Could a coldfire box be of any 
> assistance?  I have a motorola coldfire EVB with the 266MHz cpu.  I'd 
> need to get some sort of USB 2.0 card for it and USB disk storage but 
> that sort of thing isn't nearly as big of an issue with linux as it is 
> for MiNT. 

We don't have a toolchain that will help with that.

> I'll work on getting linux running on aranym unless someone already has 
> a good image for use with buildd? (that would be SO nice).  Disk space 
> is not an issue with the linux boxes and I could run 2 aranym instances 
> per box.  I don't know how everyone felt about having a buildd hosted 
> virtually rather than on real hardware.  Is that an issue?

I've been using images based on the ones here [0]. The only problem is
they are 1GB. It looks like aranym can use an IDE1 disk image, so it
would probably be easiest to put the chroots on IDE1.

I'm willing to do the work if you're willing to host. :)



[0] <http://wiki.aranym.org/afs/setup_linux>

Stephen R. Marenka     If life's not fun, you're not doing it right!

Attachment: signature.asc
Description: Digital signature

Reply to: