> -----Original Message-----
> From: Ben Collins [mailto:[EMAIL PROTECTED]]
> Sent: Friday, March 03, 2000 9:15 PM
> To: Greg Ingram
> Cc: David S. Miller; [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Giving up on RH on SPARC.
>
>
> Just to clear up some things. Linux is Linux. This isn't specific to
> RedHat. Even Debian has it's problems with sun4c. And it is
> very difficult
> to work with these systems. I know because I have only one
> sun4c system,
> and I never reboot it, even to test (that's how it got the
> 172 day uptime
> with a 2.2.9 kernel :) Most of the testing for Debian SPARC
> is done by the
> users, and they provide feedback. I rely soley on them for our
> distributions stability on this CPU class.
>
> I just don't like seeing system stability pinned on a
> distribution, when
> the core is the same no matter which one you use. It's still a Linux
> kernel no matter how you slice it. Any real gripes about a
> distribution
> are not architecture specific in 99% of the cases.
Yeah, part of that is my fault. I joined both the sparclinux @ vger, and
the sparc-linux @ redhat the same day, so I'm getting posts confused. I do
agree that most of the instability things are probably kernel specific, some
of them are specific to the python crud that RedHat does (not that they're
bad, just that the new installers need a LOT of work). That said, I'd like
to see more of the Sun4c bugs worked out, and I'll pitch in just as soon as
I get a Sun4c here again. I've seen a lot of people post with problems, but
nobody post saying "hmm... that's strange, can you do /this/ and tell me
what happens?" I don't have a clue where these problems are coming from,
just ideas on how to work around them. I'd like to see some of the people
who know more about it than I do give pointers on how to get more
information/track down this problem, and perhaps get it resolved.
Greg
-
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of the message to [EMAIL PROTECTED]
