From owner-freebsd-questions@FreeBSD.ORG Fri Mar 11 21:37:57 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D1AC6106566C for ; Fri, 11 Mar 2011 21:37:57 +0000 (UTC) (envelope-from lars@larseighner.com) Received: from mail.team1internet.com (mail.team1internet.com [216.110.13.10]) by mx1.freebsd.org (Postfix) with ESMTP id B138E8FC15 for ; Fri, 11 Mar 2011 21:37:57 +0000 (UTC) Received: from larseighner.com (unknown [216.110.13.75]) by mail.team1internet.com (Postfix) with SMTP id A3A6516B4AB; Fri, 11 Mar 2011 15:37:52 -0600 (CST) Received: by larseighner.com (nbSMTP-1.00) for uid 1001 lars@larseighner.com; Fri, 11 Mar 2011 15:37:31 -0600 (CST) Date: Fri, 11 Mar 2011 15:37:30 -0600 (CST) From: Lars Eighner X-X-Sender: lars@noos.6dollardialup.com To: Ed Flecko In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-questions@freebsd.org Subject: Re: "Best practices" on upgrading, etc. 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: Fri, 11 Mar 2011 21:37:57 -0000 On Fri, 11 Mar 2011, Ed Flecko wrote: > Hi folks, > I'm trying to fully understand the whole FBSD version thing and when, if , > and why you should consider upgrading. > > I have a production server running FBSD 8.1 (and I'm following the errata > branch) that works just fine, with no problems. > > I see that the "Production Release" of 8.2 is available. > > Obviously, 8.2 has features that 8.1 does not, but I guess my primary > questions is: > 1.) If you have a production server that's running well (and is fully > patched, i.e. following the errata branch), is there a compelling > reason to upgrade or do most people do it because there are features > in the new release that you want/need? I guess what I'm really asking > is if it makes more sense to take the "if it aint broke - don't fix > it" mindset or should you really consider upgrading when a new version > is released??? Even with backups, upgrades can be troublesome. Read the release notes. I suggest you have a reason for upgrading in mind -- other than that the number got bumped, and this goes double for a production maching. > > 2.) If I DO upgrade, I can simply change my supfile to RELENG_8_2 and then: The correct order is given in /usr/src/UPDATING. Do not rely on the following comments, but consult /usr/src/UPDATING. > > run csup > upgrade the ports Update the ports tree and ports after the OS. Otherwise, you may have to do it twice. This is not especially likely in a minor version bump, but it can happen. > make buildworld > make buildkernel > make installkernel make kernel combines the above two steps. Then as single user run mergemaster -p. > make installworld then run mergermaster and delete old if you please. -- Lars Eighner http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266