From owner-freebsd-current@FreeBSD.ORG Thu Jan 5 11:41:03 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D2A116A41F; Thu, 5 Jan 2006 11:41:03 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail04.syd.optusnet.com.au (mail04.syd.optusnet.com.au [211.29.132.185]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DC9843D5C; Thu, 5 Jan 2006 11:41:00 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail04.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k05BewI1008763 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 5 Jan 2006 22:40:58 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id k05BevHh050117; Thu, 5 Jan 2006 22:40:57 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id k05BevOZ050116; Thu, 5 Jan 2006 22:40:57 +1100 (EST) (envelope-from pjeremy) Date: Thu, 5 Jan 2006 22:40:56 +1100 From: Peter Jeremy To: Jo Rhett Message-ID: <20060105114056.GN42228@cirb503493.alcatel.com.au> References: <43A266E5.3080103@samsco.org> <20051217215434.GB92180@svcolo.com> <20051217220807.GA28741@freebie.xs4all.nl> <43A492B6.6050305@t-hosting.hu> <20051217232856.GT77268@cirb503493.alcatel.com.au> <43A4B91D.8040304@samsco.org> <20051222211730.GK39174@svcolo.com> <20051223045648.GH77268@cirb503493.alcatel.com.au> <20060105093727.GK1358@svcolo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060105093727.GK1358@svcolo.com> User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: stable@freebsd.org, current Subject: Re: FreeBSD Update is the binary update solution [Re: HEADS UP: Release schedule for 2006] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2006 11:41:03 -0000 On Thu, 2006-Jan-05 01:37:27 -0800, Jo Rhett wrote: >No. I want a binary update mechanism. Obviously if we have local >configuration options we'll have to compile our own binaries. But doing >the work of tracking system updates currently requires us to build our own >patch tracking mechanism, and then re-write it for every new release. If you're willing to do your own compiles: 1) CVSup or cvs update to whatever branch you want 2) make build{world,kernel} 3) make DESTDIR=/updates install{world,kernel} 4) mergemaster -D /updates 5) rsync or similar It seems fairly obvious that you are frustrated by FreeBSD's inability to meet your needs as far as updating is concerned. I suspect I'm not alone in being uncertain exactly what your requirements are and what additional features FreeBSD needs to satisfy you. How would you like to write a formal requirements specification and post it here (or in -arch). >It's not a recompile issue. It's a tracking/update/backout issue. I don't >mind recompiling, if I could somehow push the updates to all the right >systems and they would have it stored somewhere that they were patched... Have you looked at tools like Bcfg2 ( http://www.mcs.anl.gov/cobalt/bcfg2/ )? -- Peter Jeremy