On Sun, Jan 13, 2013 at 11:06 AM, Richard Miller <9f...@hamnavoe.com> wrote:
>>> Blue Gene
>>>
>>
>> hard to fit in the basement.
>
> How about an ipengine (mpc823)? I've got one gathering dust here.
if there's a kernel for it, and i could find, it would be great.
> I caution against working on
On 13/01/2013, at 2:21 PM, John Floren wrote:
> On Sun, Jan 13, 2013 at 11:06 AM, Richard Miller <9f...@hamnavoe.com> wrote:
Blue Gene
>>>
>>> hard to fit in the basement.
>>
>> How about an ipengine (mpc823)? I've got one gathering dust here.
>
> I caution against working on any hardware
On Sun, Jan 13, 2013 at 11:06 AM, Richard Miller <9f...@hamnavoe.com> wrote:
>>> Blue Gene
>>>
>>
>> hard to fit in the basement.
>
> How about an ipengine (mpc823)? I've got one gathering dust here.
>
>
I caution against working on any hardware which can no longer be
purchased new (sparc32, alph
>> Blue Gene
>>
>
> hard to fit in the basement.
How about an ipengine (mpc823)? I've got one gathering dust here.
On Sun, Jan 13, 2013 at 10:48 AM, erik quanstrom wrote:
> On Sun Jan 13 13:45:52 EST 2013, charles.fors...@gmail.com wrote:
>> Blue Gene
>>
>
> hard to fit in the basement.
>
> - erik
>
I don't know about the /Q's A2 processors, but you could at one point
buy PPC440 development boards, which were
On Sun Jan 13 13:45:52 EST 2013, charles.fors...@gmail.com wrote:
> Blue Gene
>
hard to fit in the basement.
- erik
Blue Gene
On 13 January 2013 18:00, Lyndon Nerenberg wrote:
> Charles, what sort of PPC hardware were you running on?
to keep everybody honest, i'd like to dig up some sort of plausable
big-endian machine. since the point here is to swat bugs, not
write a new kernel, i would be especially nice if a kernel already
existed. another big bonus would be hardware that still exists and
doesn't require a soldering iron
The distribution, I suppose, or something like it, and code we wrote.
I don't know of any publicly-available big-endian machines to test new things.
On 13 January 2013 17:45, erik quanstrom wrote:
> are you speaking of the distribution, or of plan 9 code in general?
> i was speaking of plan 9 cod
On Sun Jan 13 12:29:57 EST 2013, charles.fors...@gmail.com wrote:
> I'd be surprised if there are too many endian problems, because
> everything I tried ran happily on PowerPC
> which is usually big-endian.
are you speaking of the distribution, or of plan 9 code in general?
i was speaking of plan
I'd be surprised if there are too many endian problems, because
everything I tried ran happily on PowerPC
which is usually big-endian.
On 13 January 2013 17:08, erik quanstrom wrote:
> i'm sure that
> we're in a similar situation with endianness, but perhaps even
> worse.
as it turns out there are a lot of crazy little bugs in the system
due to running for so long on 32-bit machines. i'm sure that
we're in a similar situation with endianness, but perhaps even
worse.
to keep everybody honest, i'd like to dig up some sort of plausable
big-endian machine. since the
> Would be glad to have that patch.
/n/sources/contrib/miller/ext2srv.tar
Besides dealing with configurable-sized inodes, it allows you to
mount a 'not clean' fs read-only, instead of refusing to mount
at all.
Sorry it doesn't fix the directory-indirect-block bug.
Yes. It was me. For the timer being, I tar the dirs w/too many files in.
Would be glad to have that patch.
Thanks,
++pac
On Sat, Jan 12, 2013 at 12:47 PM, Richard Miller <9f...@hamnavoe.com> wrote:
> Somebody recently reported a problem with ext2srv not working when
> directories are huge enough
14 matches
Mail list logo
