From owner-freebsd-questions@FreeBSD.ORG Thu Nov 17 00:52:24 2005 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDC2916A41F for ; Thu, 17 Nov 2005 00:52:24 +0000 (GMT) (envelope-from iaccounts@ibctech.ca) Received: from pearl.ibctech.ca (pearl.ibctech.ca [209.167.58.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DE2343D45 for ; Thu, 17 Nov 2005 00:52:24 +0000 (GMT) (envelope-from iaccounts@ibctech.ca) Received: (qmail 3507 invoked by uid 1002); 17 Nov 2005 00:53:01 -0000 Received: from iaccounts@ibctech.ca by pearl.ibctech.ca by uid 89 with qmail-scanner-1.22 (spamassassin: 2.64. Clear:RC:1(209.167.16.15):. Processed in 7.029417 secs); 17 Nov 2005 00:53:01 -0000 Received: from unknown (HELO fuze) (209.167.16.15) by pearl.ibctech.ca with SMTP; 17 Nov 2005 00:52:53 -0000 From: "Steve Bertrand" To: "'David Kirchner'" Date: Wed, 16 Nov 2005 19:52:15 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 Thread-Index: AcXrEEWfWET4LbSyRhq6wuEZoPR+/gAABvoA In-Reply-To: <35c231bf0511161645y1dbf3f08v8e19f334847f9767@mail.gmail.com> X-Qmail-Scanner-Message-ID: <11321887756753501@pearl.ibctech.ca> Message-Id: <20051117005224.5DE2343D45@mx1.FreeBSD.org> Cc: 'FreeBSD Questions' Subject: RE: Release engineering confusion X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 00:52:25 -0000 > -----Original Message----- > From: dpkirchner@gmail.com [mailto:dpkirchner@gmail.com] On > Behalf Of David Kirchner > Sent: Wednesday, November 16, 2005 7:45 PM > To: Steve Bertrand > Cc: RW; FreeBSD Questions > Subject: Re: Release engineering confusion > > On 11/16/05, Steve Bertrand wrote: > > Thank you. However, that entire page out of the handbook > pretty much > > clarifies that a production environment should *not* track either > > STABLE or CURRENT. > > > > So I'm assuming I'm best off with RELENG_6_0 etc, etc? Does anyone > > here actually run STABLE or CURRENT in a production > environment? I've > > personally had the most luck with RELENG_4 which is still > my main box, > > but now my curiosity has got the best of me. > > > > Steve > > Ultimately it depends on how much downtime and difficulty > you're willing to endure, just in case the -STABLE branch > ends up not working for your servers for some particular > reason. We use -RELEASE almost exclusively (we have one > -STABLE machine, because we needed a newer version of a > kernel driver) as we manage hundreds of servers, and there's > no one -STABLE release (to properly describe the -STABLE > version you're using you have to have the date and time of > the cvsup, as opposed to -RELEASE versions being like > 5.4-RELEASE-p9). It's easier, and thus more reliable, for us > to have stable(heh) version strings. I can appreciate the fact it's easier to follow one string for so many servers. > If you're just working with a handful of servers, -STABLE > would probably be fine, as long as you have backups and know > how to revert to previous versions when it becomes necessary. I do only have a handful of servers, however thousands of users, and indeed, I do have backups. The problem arises in a criticality that >20 minutes of downtime would lead to a severe problem....which brings up another good question...how do YOU revert back to a previous release? If you manage so many servers, I'd love to know what type of routine you'd use to revert back (and so would many others I'd think ;) Usually, as per my last message Re: Chad, the upgrades usually fail during one or two places: buildworld, or rebooting after installkernel. Both of those are easy to recover from. *knock on wood*, I've never had a showstopper after installworld before. I wouldn't know what to do if that happened. If installkernel reboots, then I've always been good after that. Steve