[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0706151558180.27993@blackbox.fnordora.org>
Date: Fri, 15 Jun 2007 16:01:14 -0700 (PDT)
From: alan <alan@...eserver.org>
To: "Kok, Auke" <auke-jan.h.kok@...el.com>
cc: Jack Stone <jack@...keye.stone.uk.eu.org>,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
akpm@...ux-foundation.org, viro@...iv.linux.org.uk
Subject: Re: Versioning file system
On Fri, 15 Jun 2007, Kok, Auke wrote:
> Jack Stone wrote:
>> 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.
>
> <snip>
>
> have you looked into ext3cow? it allows you to take snapshots of the entire
> ext3 fs at a single point, and rollback / extract snapshots at any time
> later. This may be sufficient for you and the implementation seems to be
> rather stable already.
As long as there is only one person using the file system. Rolling back
the entire filesystem may work well for you, but screw up something else
someone else is doing.
And what kind of rights do you have to assign to the user to do that level
of snapshot and rollback? You have to assume that there are more than one
user and that they have less than root privileges.
--
"ANSI C says access to the padding fields of a struct is undefined.
ANSI C also says that struct assignment is a memcpy. Therefore struct
assignment in ANSI C is a violation of ANSI C..."
- Alan Cox
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists