All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Toomas Laasik <toomas@ac24.ee>
Cc: reiserfs-list@namesys.com
Subject: Re: Authoring a versioning plugin
Date: Fri, 13 Jan 2006 13:48:58 -0800	[thread overview]
Message-ID: <43C8204A.1050909@namesys.com> (raw)
In-Reply-To: <43C818D2.4080805@ac24.ee>

Toomas Laasik wrote:

> Hello,
> Here are some links that I have found while searching such file
> systems that can keep versions or log of changes:
> http://logfs.sourceforge.net/ - small logging filesystem project
> started by a student, but not very stable yet
> http://wayback.sourceforge.net/ - written in Perl, based on quite old
> version on FUSE API
> http://sourceforge.net/projects/cvsfs - uses CVS as file system, based
> on FUSE API
> http://www.opensolaris.org/os/community/zfs/ - very powerful file
> system that supports snapshots of files
> Microsoft has made something too on their server platform, but I
> couldn't find a link for that.
>
> It seems to me that many have started with it, but haven't finished.
> Creating a versioning FS that is comercially stable and fast takes a
> lot of effort and is quite complex. Go discover what and how others
> have done it and how to do it best in ReiserFS.
>
> I would be very interested in stable file system that supports
> automatic versioning. Maybe ReiserFS becomes the first one that I can
> actually use. I don't want a userspace FS, but a good FS where I can
> safely keep my FreeBSD installation.
>
> Toomas

Clearcase is out there and finished and it works.  Several thousand
dollars a seat though....

;-)

Hans

  reply	other threads:[~2006-01-13 21:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-11 22:59 Authoring a versioning plugin Yoanis Gil Delgado
2006-01-12  4:09 ` Hans Reiser
2006-01-12  6:44   ` Hans Reiser
2006-01-12 16:33     ` Jonathan Briggs
2006-01-12 18:33       ` Bedros Hanounik
     [not found]         ` <200601121502.32227.fred@lab.matcom.uh.cu>
2006-01-12 20:08           ` Yoanis Gil Delgado
2006-01-12 21:48         ` David Masover
2006-01-12 22:43           ` Bedros Hanounik
     [not found]             ` <200601121856.00665.fred@lab.matcom.uh.cu>
2006-01-12 23:56               ` Yoanis Gil Delgado
2006-01-13 20:59                 ` Hans Reiser
2006-01-13 16:43             ` David Masover
     [not found]     ` <200601121434.54881.fred@lab.matcom.uh.cu>
2006-01-12 20:05       ` Yoanis Gil Delgado
2006-01-12 19:13         ` Mike Benoit
2006-01-12 18:14 ` Peter van Hardenberg
     [not found]   ` <200601121439.09483.fred@lab.matcom.uh.cu>
2006-01-12 20:06     ` Yoanis Gil Delgado
2006-01-12 21:58   ` David Masover
2006-01-13 20:34   ` Hans Reiser
2006-01-13 21:17     ` Toomas Laasik
2006-01-13 21:48       ` Hans Reiser [this message]
2006-01-14 11:56       ` Pierre Etchemaïté
2006-01-13 23:00     ` Jonathan Sailor
2006-01-14  9:07       ` Peter van Hardenberg
2006-01-14 17:28         ` David Masover
2006-01-14 22:23           ` Hans Reiser

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=43C8204A.1050909@namesys.com \
    --to=reiser@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=toomas@ac24.ee \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.