From owner-freebsd-stable@FreeBSD.ORG Wed Jun 4 22:05:08 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 E86671065671 for ; Wed, 4 Jun 2008 22:05:08 +0000 (UTC) (envelope-from kdk@daleco.biz) Received: from ezekiel.daleco.biz (southernuniform.com [66.76.92.18]) by mx1.freebsd.org (Postfix) with ESMTP id 604148FC0C for ; Wed, 4 Jun 2008 22:05:08 +0000 (UTC) (envelope-from kdk@daleco.biz) Received: from localhost (localhost [127.0.0.1]) by ezekiel.daleco.biz (8.13.8/8.13.8) with ESMTP id m54Lg0AI079843; Wed, 4 Jun 2008 16:42:01 -0500 (CDT) (envelope-from kdk@daleco.biz) X-Virus-Scanned: amavisd-new at daleco.biz Received: from ezekiel.daleco.biz ([127.0.0.1]) by localhost (ezekiel.daleco.biz [127.0.0.1]) (amavisd-new, port 10024) with LMTP id xhlb3u7EOWly; Wed, 4 Jun 2008 16:41:54 -0500 (CDT) Received: from archangel.daleco.biz (dsl.daleco.biz [209.125.108.70]) by ezekiel.daleco.biz (8.13.8/8.13.8) with ESMTP id m54LfoQJ079834; Wed, 4 Jun 2008 16:41:51 -0500 (CDT) (envelope-from kdk@daleco.biz) Message-ID: <48470C19.90709@daleco.biz> Date: Wed, 04 Jun 2008 16:41:45 -0500 From: Kevin Kinsey User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.11) Gecko/20080213 SeaMonkey/1.1.7 MIME-Version: 1.0 To: cliftonr@lava.net, FreeBSD Stable References: <9B7FE91B-9C2E-4732-866C-930AC6022A40@netconsonance.com> <4846D849.2090005@FreeBSD.org> <20080604204325.GD4701@lava.net> In-Reply-To: <20080604204325.GD4701@lava.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: 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: Wed, 04 Jun 2008 22:05:09 -0000 Clifton Royston wrote: > On Wed, Jun 04, 2008 at 11:00:41AM -0700, Doug Barton wrote: >> Jo Rhett wrote: > ... >>> But given that 6.3 is still experiencing bugs with things that >>> are working fine and stable in 6.2, this is a pretty hard case to make. >> I admit to not having been following 6.x too closely, but are these >> things that have been reported, or problems you're having personally? > > Speaking just for myself, I'd love to get a general response from > people who have run servers on both as to whether 6.3 is on average > more stable than 6.2. I really haven't gotten any clear impression as > to this, either from posts on -hackers or -stable, and I believe I > asked a couple times. I've seen comments that 6.3 should be > considerably more stable than 6.2, but also complaints about bugs such > as Jo is commenting on, and I have not seen much committed in the way > of errata fixes for 6.3 since its release. > > I'd love to pick up some more stability, but I'm feeling a little > burned by 6.2 relative to 4.10, and thus twice wary. > > >>> This is also a fairly significant investment in terms of time and money >>> for any business to handle this ugprade. >> Having an upgrade path is something every operation needs. "Set it and >> forget it" isn't a viable strategy in the current culture where 0-day >> vulnerabilities are becoming increasingly common. > > Fair enough. > > Now I must confess my ignorance; is there a simplest straightforward > way to upgrade multiple servers between releases in the same branch, > other than rebuilding each from source, or wiping and reinstalling? In > the past I've always done one of those two. Define "between releases"? If you have a machine running N.NR, then freebsd-update(8), maybe? Just a thought, and that not thought through, > For example, if I take a 6.3R CD, or build one for 6-RELENG, is there > a way to do an "upgrade in place" on each server? Or would it work > better to do a build from recent source on the development server, then > export /usr/src and /usr/obj via NFS to the production servers and do > the usual "make installkernel; reboot;" etc. sequence on them? (In my > case I do have all machines on one GigE switch.) > > -- Clifton I've heard of the latter being done with decent results. Kevin Kinsey -- No amount of careful planning will ever replace dumb luck.