lkml.org 
[lkml]   [2002]   [Mar]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: filesystem transactions (was Re: linux-2.5.4-pre1 - bitkeeper testing)
From
Date
Hans Reiser <reiser@namesys.com> writes:
> Since reiser4 is in feature freeze, let's defer this thread until October, ok?
> It will be a long one I think.....

Playing with ideas is probably reasonable before then. Especially
the user space API. A couple of points were made earlier in
this thread that I would like to summarize.

1) For a filesystem level design initially treat version control,
as the snapshot/backup problem. This problem everyone
understands. If you can get and keep an atomic snapshot of
your filesystem there are some things that become easier.
2) Allow the ability to mount different versions/snapshots of the filesystem.
This ties in with the idea of per user namespaces.
3) Don't require you be root to do this stuff.

At that point you are still a long ways from a version control system
like bitkeeper but it looks like a foundation that could productively
be built on. While at the same time solving a very real user space
problem, and not messing up normal userspace filesystem semantics.

Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:25    [W:0.089 / U:0.892 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site