From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 16 15:18:35 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0CA2216A405 for ; Mon, 16 Jul 2007 15:18:35 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 72E7513C4A7 for ; Mon, 16 Jul 2007 15:18:33 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from [10.0.0.222] (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id l6GFIOH7015610; Mon, 16 Jul 2007 08:18:33 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <469B8C40.9020603@freebsd.org> Date: Mon, 16 Jul 2007 08:18:24 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matthew Seaman References: <46992FFF.7010906@kientzle.com> <20070714223853.GF16579@britannica.bec.de> <469992CA.6000104@freebsd.org> <4699BE75.2090808@freebsd.org> <20070715133016.GA53853@psconsult.nl> <469A6B73.1030004@freebsd.org> <469B23FE.8060608@infracaninophile.co.uk> In-Reply-To: <469B23FE.8060608@infracaninophile.co.uk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Tar output mode for installworld X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jul 2007 15:18:35 -0000 > Being able to record a series of incremental changes in a filesystem > hierarchy, and then roll them back as required. That would be > exceedingly useful, and I think your 'ntree' format has virtually > everything necessary to do that. The most obvious missing bit I can > see is creating a backup of a file before overwriting it with > different content. Is this something that requires changes to the specification file format, or just a feature of the tool that uses the specification file? If the former, what do you envision would be required? Tim Kientzle