From owner-freebsd-stable@FreeBSD.ORG Thu Jun 5 00:35:51 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 6698A106567F; Thu, 5 Jun 2008 00:35:51 +0000 (UTC) (envelope-from edwin@mavetju.org) Received: from mail5out.barnet.com.au (mail5.barnet.com.au [202.83.178.78]) by mx1.freebsd.org (Postfix) with ESMTP id 1500D8FC1F; Thu, 5 Jun 2008 00:35:51 +0000 (UTC) (envelope-from edwin@mavetju.org) Received: by mail5out.barnet.com.au (Postfix, from userid 1001) id 5E6492218C0E; Thu, 5 Jun 2008 10:35:50 +1000 (EST) X-Viruscan-Id: <484734E40000F821EDA702@BarNet> Received: from mail5auth.barnet.com.au (mail5.barnet.com.au [202.83.178.78]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail5auth.barnet.com.au", Issuer "*.barnet.com.au" (verified OK)) by mail5.barnet.com.au (Postfix) with ESMTP id 63A5D21B3618; Thu, 5 Jun 2008 10:35:48 +1000 (EST) Received: from k7.mavetju (k7.mavetju.org [10.251.1.18]) by mail5auth.barnet.com.au (Postfix) with ESMTP id 8C4852218BEB; Thu, 5 Jun 2008 10:35:46 +1000 (EST) Received: by k7.mavetju (Postfix, from userid 1001) id EA38915C; Thu, 5 Jun 2008 10:35:45 +1000 (EST) Date: Thu, 5 Jun 2008 10:35:45 +1000 From: Edwin Groothuis To: Jo Rhett Message-ID: <20080605003545.GP89632@k7.mavetju> Mail-Followup-To: Edwin Groothuis , Jo Rhett , Steven Hartland , Doug Barton , FreeBSD Stable References: <458FE12C-AE4D-48F9-8193-4663079CEEF8@netconsonance.com> <84EBEA5D3A1F47E79E8E12C4CF4D0314@multiplay.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: FreeBSD Stable , Doug Barton , Steven Hartland 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:35:51 -0000 On Wed, Jun 04, 2008 at 05:24:42PM -0700, Jo Rhett wrote: > On Jun 4, 2008, at 5:17 PM, Steven Hartland wrote: > >I wouldn't be surprised if these are not new bugs, just something > >that others have noticed later than 6.2 and I'd suggest you actually > >try 6.3 to see if they are in fact an issue for you. > > I don't have the resources to load up the systems enough to find these > problems sitting on my desk. And I can't risk production resources > for problems known and reported on the *EXACT* same hardware. > > "oh but it won't happen to me" isn't a useful methodology in a > production environment. > > I mean, seriously, I know the majority of you are happy rebooting your > systems 5x daily to run the latest. I'll do that with my home system, > no problem. But I can't do this in a production environment. Use the eat-your-own-food approach (while not knowing what the 500 systems do): Make sure you use the same hardware and software as what is in production. Upgrade it first, run it for two weeks. If it doesn't, fallback and see where it went wrong. If it all works fine after two weeks, roll it out. Edwin -- Edwin Groothuis | Personal website: http://www.mavetju.org edwin@mavetju.org | Weblog: http://www.mavetju.org/weblog/