From owner-freebsd-questions@FreeBSD.ORG Tue Jun 8 15:28:47 2004 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 88C9316A4CE for ; Tue, 8 Jun 2004 15:28:47 +0000 (GMT) Received: from dyer.circlesquared.com (host217-45-219-83.in-addr.btopenworld.com [217.45.219.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B20243D55 for ; Tue, 8 Jun 2004 15:28:42 +0000 (GMT) (envelope-from peter@circlesquared.com) Received: from circlesquared.com (localhost.petanna.net [127.0.0.1]) i58FVTXK048900; Tue, 8 Jun 2004 16:31:30 +0100 (BST) (envelope-from peter@circlesquared.com) Message-ID: <40C5DBD1.5010607@circlesquared.com> Date: Tue, 08 Jun 2004 16:31:29 +0100 From: Peter Risdon User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7b) Gecko/20040327 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vince Hoffman References: <40C5BCAC.6090401@circlesquared.com> <20040608144433.D31793@unsane.co.uk> In-Reply-To: <20040608144433.D31793@unsane.co.uk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: FreeBSD Question List Subject: Re: Wisdom of automating upgrades 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: Tue, 08 Jun 2004 15:28:47 -0000 Vince Hoffman wrote: >On Tue, 8 Jun 2004, Peter Risdon wrote: > > >>I have been pondering the wisdom >>of automating the upgrade process, >> >> >You may want to have a look at freebsd-update. Its a binary updater, >Client/Server config, the server code and info on what it is, is available >from http://www.daemonology.net/freebsd-update/ >and the client is in ports. > >Vince > > Thanks very much for this. I was vaguely aware of freebsd-update (I think it's been mentioned on this list). But since it seems only to be concerned with security updates it forms a subset (albeit vital) of a complete upgrade. I suppose what I'm driving at is whether the RELENG_4 branch sees many commits that are likely to be problematic. My experience of it, which is both fairly random and limited, is excellent. I don't remember having any problems with a kernel/world upgrade within a production branch. Doing a batch of upgrades today simultaneously and remotely, and all going fine as usual, made me think of this again. Peter.