Date: Tue, 25 May 1999 13:31:23 -0400 (EDT) From: Vince Vielhaber <vev@michvhf.com> To: Wilko Bulte <wilko@yedi.iaf.nl> Cc: Seth <seth@freebie.dp.ny.frb.org>, serge69@nym.alias.net, freebsd-stable@FreeBSD.ORG Subject: Re: [Q] How stable is FreeBSD 3.X ? Message-ID: <Pine.BSF.4.05.9905251321550.3974-100000@paprika.michvhf.com> In-Reply-To: <199905251530.RAA15405@yedi.iaf.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 25 May 1999, Wilko Bulte wrote:
> As Seth wrote ...
>
> > Why not upgrade to -STABLE and solve the problem? I also had panics under
> > 3.1-RELEASE, but they were all fixed within one week of -STABLE upgrades.
>
> I agree this may fix it. But it does not address the original point of
> Sergey: why should I need to go for V.next if I just got my V.today with
> -RELEASE stamped on it?
>
> Mind you, there are more than enough answers to that question. One of the
> major ones is the fact that FreeBSD is a volunteer effort. We don't have
> paid people to test it on a gazillion different hardware platforms.
>
> If you think that is not relevant: I used to work with the SCO Unix source
> base and the amount of comment on hardware quirks is considerable to say the
> least.
>
> No instant answers I guess,.
I'm leaving Sergey's original in place so everyone can reread it. From
the vast amount of information he gives (and has given in subsequent
followups) what alternate advice can anyone give him? 3.2-R happened
ten days ago, so if he got V.today or even V.yesterday he'd be using
3.2. There is no mention to the hardware used or even what other software
he's using. How about what he's doing when it fails? Is he by chance
overclocking? Who knows? In another post he says it's up to the
developers to ask him questions. If he doesn't want to volunteer the
conditions surrounding the problems he's having with an OS that came out
a few months ago, the only answer can be to upgrade to the current
version.
>
> > On Tue, 25 May 1999, Sergey wrote:
> >
> > > Hi!
> > >
> > > I've checked this out on good hardware. And now can CLAIM that
> > > 3.1-R *really* have kernel problems on FreeBSD's "classic" configuration.
> > > This bug causes TERRIBLE instability - panic in 24 hours. Even Microsoft's
> > > OSes gives significantly better results
> > >
> > >
> > >
> > > This is mourning day for me - I CAN'T believe in stability of RELEASES
> > > any more...
> > >
> > >
> > > With best regards, Sergey.
Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null
# include <std/disclaimers.h> TEAM-OS2
Online Campground Directory http://www.camping-usa.com
Online Giftshop Superstore http://www.cloudninegifts.com
==========================================================================
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9905251321550.3974-100000>