linux-kernel - Re: Versioning file system

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4676B947.4010707@zytor.com>
Date:	Mon, 18 Jun 2007 09:56:39 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Jack Stone <jack@...keye.stone.uk.eu.org>
CC:	Bryan Henderson <hbryan@...ibm.com>, alan <alan@...eserver.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

Jack Stone wrote:
>>
>> Later, I discovered what I think are superior alternatives:  RCS-style 
>> version management on top of the filesystem, and automatic versioning 
>> based on time instead of count of "modifications."  For example, make a 
>> copy of every changed file every hour and keep it for a day and keep one 
>> of those for a week, and keep one of those for a month, etc.  This works 
>> even without snapshot technology and even without sub-file deltas.  But of 
>> course, it's better with those.
> 
> From what I can see this seems to be the consesus (and it sound very
> sensible to me).
> 
> The question remains is where to implement versioning: directly in
> individual filesystems or in the vfs code so all filesystems can use it?
> 

More likely a shim filesystem on top would be a better option.

	-hpa
-
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/