From owner-freebsd-stable@FreeBSD.ORG Sun Feb 27 03:38:50 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 3E3191065675; Sun, 27 Feb 2011 03:38:50 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from doug-optiplex.ka9q.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 00282156FAD; Sun, 27 Feb 2011 03:38:33 +0000 (UTC) Message-ID: <4D69C739.6050002@FreeBSD.org> Date: Sat, 26 Feb 2011 19:38:33 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.13) Gecko/20110129 Thunderbird/3.1.7 MIME-Version: 1.0 To: Jason Helfman References: <4D66CCFF.9020903@buffalo.edu> <20110225160109.GA32260@lava.net> <20110225180019.GD76063@eggman.experts-exchange.com> <201102251501.11318.jhb@freebsd.org> <20110227025512.GA64170@eggman.experts-exchange.com> In-Reply-To: <20110227025512.GA64170@eggman.experts-exchange.com> X-Enigmail-Version: 1.1.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, cperciva@freebsd.org, John Baldwin Subject: Re: 8.2/7.4-RELEASEs Announced... 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, 27 Feb 2011 03:38:50 -0000 When I was looking at this problem myself recently it occurred to me that one way to handle it would be to have the freebsd-update code build and populate the temproot directory that mergemaster uses and then offer the user the option to use that alternative. The process could use something like what's done in src/release/scripts/mm-mtree.sh if this direction is desirable. Obviously the temproot directory would have to be distributed as an additional blob by freebsd-update, but this method has the advantage of reusing existing tools, and it's able to handle updates from arbitrarily old existing installations. hth, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/