From owner-freebsd-hackers Sat Dec 4 21:53:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id A142B14EE3; Sat, 4 Dec 1999 21:53:11 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id VAA13186; Sat, 4 Dec 1999 21:52:13 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id VAA16014; Sat, 4 Dec 1999 21:52:12 -0800 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA03842; Sat, 4 Dec 99 21:52:09 PST Message-Id: <3849FD95.F0434263@softweyr.com> Date: Sat, 04 Dec 1999 22:52:21 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Matthew Dillon Cc: Kris Kennaway , freebsd-hackers@FreeBSD.ORG Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) References: <199912050514.VAA58998@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > : > :Since I'm one of the existing FreeBSD people you're probably referring to > :here, let me remind you of the actual content: > : > :Dennis said the following: > : > :> The nightmare of instability of 3.x continues whilst the braintrust > :> flogs away at 4.x. Its really a damn shame. And why is 3.x so much > :> slower than 2.2.8? Will 4.0 be slower yet? > : > :Note the apparently belligerent tone, including use of emotionally charged > :language and sudden change of topic. Now, when someone makes a wild, > :authoritative yet unsupported statement like this, I think it's only > :reasonable to ask for some evidence. If I sounded facetious when I said: > > He didn't say this until after the situation had started to degrade. > > Besides, he's right. 3.x has serious problems. All running software has serious problems, that's why it is never considered done. Taking the time to enumerate specific problems that are currently plaguing an installation is the only way anyone can possibly hope to help. Problems reports of "It don't work" are helpful to absolutely noone. > For a while I had > good hopes for 4.x but so many things have been changed gratuitously > (and not by me!) that I'm beginning to worry about 4.x as well. I think > the problem is that we split the tree too early and everyone moved to > developing on 4.x. > > Perhaps this time around we should not split out the 5.x tree until we've > gotten past the 4.1 release. It's something to think about. Finally, a well-thought-out message in this thread. I'd say rather than rubber-stamping it at 4.1, perhaps stretch it to "a 4.x that we'd recommend to Yahoo!" Of course, 4.1 *should* be that stable. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message