From owner-freebsd-bugbusters@FreeBSD.ORG Thu Oct 20 09:04:24 2005 Return-Path: X-Original-To: bugbusters@FreeBSD.org Delivered-To: freebsd-bugbusters@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3845216A41F for ; Thu, 20 Oct 2005 09:04:24 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD01043D66 for ; Thu, 20 Oct 2005 09:04:23 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id E54C13048; Thu, 20 Oct 2005 04:04:20 -0500 (CDT) Date: Thu, 20 Oct 2005 04:04:19 -0500 To: "Bill Schmitt (SW)" Message-ID: <20051020090419.GA24776@soaustin.net> References: <435759FB.6070301@schmittnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <435759FB.6070301@schmittnet.com> User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) Cc: bugbusters@FreeBSD.org Subject: Re: [Fwd: Bug followup?] X-BeenThere: freebsd-bugbusters@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Coordination of the Problem Report handling effort." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Oct 2005 09:04:24 -0000 On Thu, Oct 20, 2005 at 04:48:59AM -0400, Bill Schmitt (SW) wrote: > I have received comments from other users with similar problems, but > can't seem to raise anyone in development. Can you help? The response is all driven by developer time and interest. From what I can tell from the GNATS statistics, the 'kern' PRs that are coming in are primarily from 6.0 and secondarily from 5.4 and -CURRENT systems. Almost none come in from 4.X. (The commits are almost entirely to 6.0 and -CURRENT at this point). This, to me, indicates that this is where the src developers are doing all their work. The disk code in 6.0 has been rewritten twice since the 4.9 days and is thus not instructive for you. I can't really give you much more to go on than that. It would take someone with the exact same hardware who could do a binary search of the source changes to narrow down exactly when things broke. The reality of the situation is that we have far more demand for developers than we have developers. mcl