From owner-freebsd-stable@FreeBSD.ORG Wed Jun 4 23:39:06 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 480231065677 for ; Wed, 4 Jun 2008 23:39:06 +0000 (UTC) (envelope-from cliftonr@lava.net) Received: from outgoing01.lava.net (cake.lava.net [IPv6:2001:1888:0:1:230:48ff:fe5b:3b50]) by mx1.freebsd.org (Postfix) with ESMTP id E9D1A8FC21 for ; Wed, 4 Jun 2008 23:39:05 +0000 (UTC) (envelope-from cliftonr@lava.net) Received: from malasada.lava.net (malasada.lava.net [64.65.64.17]) by outgoing01.lava.net (Postfix) with ESMTP id 90142D0408; Wed, 4 Jun 2008 13:39:05 -1000 (HST) Received: by malasada.lava.net (Postfix, from userid 102) id 08B96153882; Wed, 4 Jun 2008 13:39:04 -1000 (HST) Date: Wed, 4 Jun 2008 13:39:04 -1000 From: Clifton Royston To: Greg Byshenk Message-ID: <20080604233903.GA1146@lava.net> Mail-Followup-To: Greg Byshenk , FreeBSD Stable References: <9B7FE91B-9C2E-4732-866C-930AC6022A40@netconsonance.com> <4846D849.2090005@FreeBSD.org> <20080604204325.GD4701@lava.net> <48470C19.90709@daleco.biz> <20080604232135.GD1381@core.byshenk.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080604232135.GD1381@core.byshenk.net> User-Agent: Mutt/1.4.2.2i 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: Wed, 04 Jun 2008 23:39:06 -0000 On Thu, Jun 05, 2008 at 01:21:35AM +0200, Greg Byshenk wrote: > On Wed, Jun 04, 2008 at 04:41:45PM -0500, Kevin Kinsey wrote: > > Clifton Royston wrote: > > > > 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.) > > > I've heard of the latter being done with decent results. > > I can't say that it is "better", but I do the latter (well, actually I > build on a test machine to make sure there are no problems, then sync > to an NFS server and mount src and object from there, followed by > installkernel-reboot-installworld-merge-reboot) Actually, yes, that's precisely what I was planning. I *do* at least have a separate development and test machine, apart from the main server cluster. > on a number of different > machines (currently runnign 6.3-STABLE of 2008-05-22 and 7.0-STABLE of > 2008-05-27), and it is certainly faster and easier than doing a build > on each individual machine. > > I do the same thing with ports, doing a 'portupgrade -p' on the build > machine followed by a 'portupgrade -P' on the "clients" (building > packages on the build machine, and then installing via my own packages > on the others). Again, I can't say that it is "better", but it is > certainly faster and easier. Thanks a lot for the feedback! I'll have to consider freebsd-update too; I simply haven't got used to its being available as an option. -- Clifton -- Clifton Royston -- cliftonr@iandicomputing.com / cliftonr@lava.net President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services