Kyle Moffett wrote:
On Jun 18, 2007, at 13:56:05, Bryan Henderson wrote:
The question remains is where to implement versioning: directly in
individual filesystems or in the vfs code so all filesystems can use it?
Or not in the kernel at all. I've been doing versioning of the types
I
Chris Snook wrote:
But what you're talking about *will* break userspace. If I do an ls in
a directory, and get pages upon pages of versions of just one file,
that's broken. If I tar up a directory and get a tarball that's
hundreds of times larger than it should be, that's broken. If you
H. Peter Anvin wrote:
Chris Snook wrote:
I pointed out NetApp's .snapshot directories because that's a method
that uses legal path character, but doesn't break anything. With this
method, userspace tools will have to be taught that : is suddenly a
special character.
Not to mention that
H. Peter Anvin wrote:
Jack Stone wrote:
But that would cause havoc with shells which use ; to seperate commands.
Using ; would defiantly break userspace
Not really. It's just a bit awkward to use, but so's the whole concept.
I think we can all agree on that after this thread but I still
Chris Snook wrote:
Jack Stone wrote:
The idea was that if you did an ls you would get the latest version of
the file without the :revision_num. The only visible version would be
the latest version, i.e. the current system would not change. The idea
was that it would only show earlier versions
Chris Snook wrote:
Jack Stone wrote:
H. Peter Anvin wrote:
Chris Snook wrote:
I pointed out NetApp's .snapshot directories because that's a method
that uses legal path character, but doesn't break anything. With this
method, userspace tools will have to be taught that : is suddenly
Chris Snook wrote:
Okay, so now you have to modify ls, cp, tar, and thousands of other
applications to be aware of the versioning, otherwise you can't use it.
Please don't get hung up on the interface. This is a really cool
feature that will require some serious engineering work to make it
John Stoffel wrote:
Jack == Jack Stone [EMAIL PROTECTED] writes:
Jack The whole idea of the file system is that it wouldn't return the
Jack file in the file listing. The user would have to know that the
Jack file system was versioning to access the older versions as they
Jack would
Andreas Dilger wrote:
Too bad everyone is spending time on 10 similar-but-slightly-different
filesystems. This will likely end up with a bunch of filesystems that
implement some easy subset of features, but will not get polished for
users or have a full set of features implemented (e.g. ACL,
Bryan Henderson wrote:
Part of the problem is that whenever you modify a file
is ill-defined, or rather, if you were to take the literal meaning of it
you'd end up with an unmanageable number of revisions.
Let me expand on that. Do you want to save a revision every time the user
types in
alan wrote:
On Fri, 15 Jun 2007, H. Peter Anvin wrote:
This is one of those things that seems like a good idea, but frequently
ends up short. Part of the problem is that whenever you modify a file
is ill-defined, or rather, if you were to take the literal meaning of it
you'd end up with an
Chris Snook wrote:
The underlying internal implementation of something like this wouldn't
be all that hard on many filesystems, but it's the interface that's the
problem. The ':' character is a perfectly legal filename character, so
doing it that way would break things.
But to work without
Jeffrey V. Merkey wrote:
When you get into the recycling issues with storage, the patents come
into play. Also, using the file name to reference revisions is already
the subject of a patent previously filed (I no longer own the patent, I
sold them to Canopy). There is a third one about to be
Jan Harkes wrote:
Sites like portal.acm.org and citeseer.ist.psu.edu are good places to
find copies of these papers. They also provide links to other work that
either is cited by, or cites these papers which is a convenient way to
find other papers in this area.
Researching, designing and
I hope I got the CC list right. Apologies to anyone in didn't include
and anyone I shouldn't have included.
The basic idea is to include an idea from VMS that seems to be quite
useful: version numbers for files.
The idea is that whenever you modify a file the system saves it to na
new copy
[EMAIL PROTECTED] wrote:
On Sun, 10 Jun 2007, Pavel Machek wrote:
But you have that regex in _user_ space, in a place where policy
is loaded into kernel.
then the kernel is going to have to call out to userspace every time a
file is created or renamed and the policy is going to be enforced
16 matches
Mail list logo
