From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 18:31: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 597481065671 for ; Sun, 8 Jun 2008 18:31:20 +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 EE7EB8FC15 for ; Sun, 8 Jun 2008 18:31:19 +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 59B0AD00F0; Sun, 8 Jun 2008 08:31:17 -1000 (HST) Received: by malasada.lava.net (Postfix, from userid 102) id D38FA153882; Sun, 8 Jun 2008 08:31:15 -1000 (HST) Date: Sun, 8 Jun 2008 08:31:15 -1000 From: Clifton Royston To: Steven Hartland Message-ID: <20080608183114.GA3049@lava.net> Mail-Followup-To: Steven Hartland , "Patrick M. Hausen" , Jo Rhett , FreeBSD Stable References: <48472CCF.8080101@FreeBSD.org> <20080608094534.GA58022@hugo10.ka.punkt.de> <650DAC4C127C447BA6215850F906CC09@multiplay.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <650DAC4C127C447BA6215850F906CC09@multiplay.co.uk> User-Agent: Mutt/1.4.2.2i Cc: Jo Rhett , 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: Sun, 08 Jun 2008 18:31:20 -0000 On Sun, Jun 08, 2008 at 12:18:22PM +0100, Steven Hartland wrote: > ----- Original Message ----- > From: "Patrick M. Hausen" > > >I have never ever had a single problem caused by running RELENG_N. > >We changed that only because as the number of machines increases > >it pays to run the same software on all of them, and "RELEASE" > >provides a convenient (!) reference point for that. Yet, if I were > >affected by a particular bug in RELENG_6_3, I would simply pick > >my own later reference point at which the bug is fixed. > > An alternative to this is to maintain a specific set of patches > to -RELEASE for only the issues / fixes that you are experiencing. > > This has worked very well for us over the years so I can recommend > it as well. I've done this too. I kept a private 4.8 for years updated with driver and security patches from 4.9 et seq. once 4.8 support was discontinued. Just do the source checkout via CVS and create your own CVS branch. It is more work than I'm prepared for now, where the FreeBSD systems I'm supporting is part-time consulting; that's why I decided to jump to a release line. However, it's a reasonable option for someone who's maintaining their own larger groups of systems. -- 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