From owner-freebsd-questions@FreeBSD.ORG Fri Nov 21 08:10:10 2003 Return-Path: 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 E2A2716A4CE for ; Fri, 21 Nov 2003 08:10:10 -0800 (PST) Received: from anon.securenym.net (anon.securenym.net [209.113.101.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7533243F75 for ; Fri, 21 Nov 2003 08:10:07 -0800 (PST) (envelope-from dincht@securenym.net) Received: (from root@localhost) by anon.securenym.net (8.11.7/8.11.7) id hALG7KL01535 for freebsd-questions@freebsd.org.filtered; Fri, 21 Nov 2003 10:07:20 -0600 (CST) Message-Id: <200311211607.hALG7KL01535@anon.securenym.net> X-Securenym: dincht From: "C. Ulrich" To: Peter Risdon In-Reply-To: <3FBE01AD.5060102@circlesquared.com> References: <200311211051.hALApOp79560@fat_man.ascendency.net> <3FBE01AD.5060102@circlesquared.com> Content-Type: text/plain Organization: The Peter Jennings Fan Club Mime-Version: 1.0 Date: Fri, 21 Nov 2003 12:06:54 -0500 Content-Transfer-Encoding: 7bit cc: mike@ascendency.net cc: freebsd-questions@freebsd.org Subject: Re: Downgrading from current to release or stable? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Nov 2003 16:10:11 -0000 On Fri, 2003-11-21 at 07:14, Peter Risdon wrote: > I just moved from 5.1-current to 5.1 release, and fixed a lot of > problems on a horribly unstable box by doing so. I believe downgrading > to stable is very awkward, but others will be better qualified to > discuss that than I am. On a related note, I know that following CURRENT is a game of risk, but are current branch releases (such as 5.1-RELEASE) intended to be a bit more stable and usable than staying constantly up to date with CURRENT? In other words, is there a pretty good chance that 5.2-RELEASE won't break my (non-production) workstation too horribly when it comes out? Or does it carry the same exact risks as following CURRENT? Thanks, Charles Ulrich -- http://bityard.net