Date: Mon, 16 Jul 2007 08:53:34 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Tim Kientzle <kientzle@freebsd.org> Cc: freebsd-hackers@freebsd.org Subject: Re: Tar output mode for installworld Message-ID: <469B23FE.8060608@infracaninophile.co.uk> In-Reply-To: <469A6B73.1030004@freebsd.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Tim Kientzle wrote:
> Paul Schenkeveld wrote:
>> Having a file describing everything that gets installed would also
>> benefit
>> later upgrades to a system.
>
> One of my questions: Does my proposed format suffice for these
> other purposes? If not, what other features would be required?
> Is it worth trying to design a single format that handles these
> various cases?
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.
Cheers,
Matthew
- --
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGmyP+8Mjk52CukIwRCGaUAJ0c8j9l4h08dIRBY8bFuX0XA/v4HgCfR7iX
F0BjIjIz0ds+EEV74H/JIBs=
=J76U
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?469B23FE.8060608>