From owner-freebsd-stable@FreeBSD.ORG Thu Jun 5 00:44:20 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 794F01065676 for ; Thu, 5 Jun 2008 00:44:20 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 299728FC15 for ; Thu, 5 Jun 2008 00:44:20 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.local ([192.168.254.200]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id m550iGjE090254; Wed, 4 Jun 2008 18:44:17 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <484736E0.6090004@samsco.org> Date: Wed, 04 Jun 2008 18:44:16 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 MIME-Version: 1.0 To: Jo Rhett References: <9B7FE91B-9C2E-4732-866C-930AC6022A40@netconsonance.com> <4846E637.9080101@samsco.org> <48472DB6.5030909@samsco.org> <6010676B-91B0-4AF8-ACF8-039A59B29331@netconsonance.com> In-Reply-To: <6010676B-91B0-4AF8-ACF8-039A59B29331@netconsonance.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.4 required=3.8 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: FreeBSD Stable Subject: Re: challenge: end of life for 6.2 is premature with buggy 6.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jun 2008 00:44:20 -0000 Jo Rhett wrote: > > On Jun 4, 2008, at 5:05 PM, Scott Long wrote: >> Jo Rhett wrote: >>> On Jun 4, 2008, at 12:00 PM, Scott Long wrote: >>>> Can you describe the bugs that are affecting you? >>> gmirror failures, 3ware raid driver timeouts, bge0 problems. All >>> three in production use on dozens of systems. >> >> Give me specific details on the 3ware and bge problems. > > > Familiar with searching the open bug reports? That's where I found them. > > Sorry, I'm knee-deep in a major project that I've been working 16+ hours > a day on right now, and I just don't have the time for spurious > queries. Query the open bug reports for 6.3 and then explain to me > again why 6.2 is no longer supported. > Really, if it's such a big issue that you have time to bitch an moan on the mailing lists, I don't understand why you don't have time to also help a goddamned developer identify the problem. Are you actually experiencing problems with 6.3, or not? Scott