Date: Sat, 26 Feb 2011 19:38:33 -0800 From: Doug Barton <dougb@FreeBSD.org> To: Jason Helfman <jhelfman@e-e.com> Cc: freebsd-stable@freebsd.org, cperciva@freebsd.org, John Baldwin <jhb@freebsd.org> Subject: Re: 8.2/7.4-RELEASEs Announced... Message-ID: <4D69C739.6050002@FreeBSD.org> In-Reply-To: <20110227025512.GA64170@eggman.experts-exchange.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D69C739.6050002>