From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Sun,  4 Jan 2009 21:19:35 -0800
From: "Roman V. Shaposhnik" <rvs@sun.com>
In-reply-to: <2343f07a0d7a83b20c12ce62351ce086@quanstro.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Message-id: <1231132775.11463.473.camel@goose.sun.com>
MIME-version: 1.0
Content-type: text/plain
Content-transfer-encoding: 7BIT
References: <2343f07a0d7a83b20c12ce62351ce086@quanstro.net>
Subject: Re: [9fans] Changelogs & Patches?
Topicbox-Message-UUID: 797bd74c-ead4-11e9-9d60-3106f5b1d025

On Mon, 2008-12-29 at 19:57 -0500, erik quanstrom wrote:
> history is not a property of venti.  venti is a sparse virtual drive
> with ~2^80 bits storage.  blocks are addressed by sha1 hash of
> their content. fossil is the fileserver.  the analogy would be a change
> in fossil format.  my technique would work for fossil, too.

I see now. Its interesting to note how it seems to map the division
of labor in ZFS, where we have ZFS pools as virtual drives. Now
that I've mentioned it, I think it'll do me good to try and evaluate
fossil/venti through the lens of ZFS. I guess its not a coincedence
that ZFS actually has a built-in support for the kind of history
transfer you were implementing.

Thanks,
Roman.