From: Kent Borg <kentborg@borg.org>
To: linux-kernel@vger.kernel.org
Cc: "Kerl, John" <John.Kerl@Avnet.com>, "'Lars Marowsky-Bree'" <lmb@suse.de>
Subject: Re: Versioning File Systems?
Date: Thu, 18 Apr 2002 14:14:56 -0400 [thread overview]
Message-ID: <20020418141456.A16866@borg.org> (raw)
In-Reply-To: <C08678384BE7D311B4D70004ACA371050B7633CA@amer22.avnet.com> <20020418172419.GA433@iucha.net>
On Thu, Apr 18, 2002 at 12:24:19PM -0500, Florin Iucha wrote:
> http://www.netcraft.com.au/geoffrey/katie/
Very interesting.
Looking at the docs that come in the sources Katie appears to be
(mostly) perl code that stores its data in Postgresql and uses NFS to
loop it back as filesystem of normal looking files, hidden directories
for access to old versions, and command a line program for doing all
other CVS-ish functions.
Glad to see there is such a nice conceptual testbed for what I was
looking for, but this isn't it directly.
Am I crazy or would it be possible to create a versioning file system
on the model of the cannonical ext2? It would sit on top of a rather
stupid block device and present something that, at first glance, looks
like a traditional filesystem. A complete superset, create a file by
creating a file, read a file by reading a file, delete a file by
deleting a file, and make it all happen at a low enough level to boot
from it even.
The extra features would, of course, need additional means for access;
I don't know the ramifications of a such a complete filesystem having
such things like extra hidden-ish directories for accessing old
versions. (I worry about standard utilities tripping over virtual
contents--I know that /proc and /dev do strange things when I forget
and pretend they are simply files.)
-kb
next prev parent reply other threads:[~2002-04-18 18:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 16:51 Versioning File Systems? Kerl, John
2002-04-18 17:24 ` Florin Iucha
2002-04-18 18:14 ` Kent Borg [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-18 15:05 Kent Borg
2002-04-18 15:20 ` Larry McVoy
2002-04-18 15:27 ` Lars Marowsky-Bree
2002-04-18 16:55 ` Kent Borg
2002-04-18 17:04 ` Joshua MacDonald
2002-04-20 8:44 ` Thomas Zimmerman
2002-04-18 23:19 ` Stevie O
2002-04-19 4:12 ` Mark Mielke
2002-04-18 18:11 ` Jeremy Jackson
2002-04-23 22:42 ` Bill Davidsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020418141456.A16866@borg.org \
--to=kentborg@borg.org \
--cc=John.Kerl@Avnet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lmb@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox