On Sat, 19 Feb 2000, Bart van der Ouderaa wrote:

> panic: mesh: FIFO != 0
> Stopped in  at  0x2386e0:       lwz r0, r1, 0x14,
> db>

> btw how stabile is the snapshot?

given that the -release branch panic'ed before you even started using it,
if the snapshot doesn't panic then no matter what the snapshot does from
boot onward I think it's almost by definition _more_ stable than release,
on your Macintosh at least. :)

seriously, i wouldn't worry about it.  Stability is relative, you know
what I mean?  NetBSD stability is then hypothetically measured relative to
-release of a popular port to sane hardware, like sparc or alpha.  In my
experience (and i do have exactly this experience), when NetBSD developers
say something ``isn't stable,'' it's still more stable than, oh, say,
Linux for example. Considering that's the alternative, you win either way,
-release or -current.

and frankly i'm not sure macppc is mature enough that -release is more
stable than -current, even in general (as opposed to on your machine where
it definitely isn't :).

this is how i look at it, though:

it's usually more fun to develop software that gets used, write books that
get read, u.s.w.  given how many of us there are using macppc, would you
rather motivate actual work on the development branch, or rework and
pullups on the release branch?

anyway, i think it'd be great if you are able to make the time commitment
to using -current, as i'm sure the port could use your help finding the
problems and testing the solutions.  besides, it looks like macppc is
developing rapidly enough that the improved features (and stability :) of
-current is worth your time, IMHO.

-- 
Miles Nordin / v:+1 720 841-8308 fax:+1 530 579-8680
555 Bryant Street PMB 182 / Palo Alto, CA 94301-1700 / US