Date: Mon, 06 Dec 1999 14:34:42 -0500 From: Dennis <dennis@etinc.com> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: hackers@freebsd.org Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) Message-ID: <199912061939.OAA22030@etinc.com> In-Reply-To: <199912061905.LAA71515@apollo.backplane.com> References: <19991205120428.E6F4514C3E@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At 11:05 AM 12/6/99 -0800, you wrote: > >: >: >:[snip] >:> I am a good programmer and can fix things :-). But I've had to deal with >:> a number of nightmare situations by commercial entities deploying FreeBSD >:> and at least three (including one very recently) where commercial entities >:> have refused to upgrade past 2.2.x due to perceived stability problems. >:[snip] >:> >:> -Matt >:> Matthew Dillon >: >: we can not identify the specific problem from this message. >:without sufficient information to indentify and hopefully reproduce >:the problem, we can not address it. please provide this information >:if it is available to you. if it is not, please provide us contact >:information for the commercial entities experiencing the problem. >: >:jmb > > First, the statement was anecdotal -- all of the problems have been > fixed in -current. THIS is EXACTLY what I was saying. What good does it do anyone in a commercial environment that its fixed in -current? Thats the reason we dumped NetBSD, because everyone was using -current the the releases were always unstable. Of course moving to -current to fix the problems in 3.x introduce a whole new set of problems, in which case you have an OS that is never going to be stable. When 4.0 is released we'll be told that the problems of 4.0 are fixed in -current. When does it end? DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199912061939.OAA22030>