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]

Date:	Sat, 16 Jun 2007 09:11:24 +0100
From:	Jack Stone <jack@...keye.stone.uk.eu.org>
To:	alan <alan@...eserver.org>
CC:	hpa@...or.com, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org, akpm@...ux-foundation.org,
	viro@...iv.linux.org.uk
Subject: Re: Versioning file system

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 unmanageable number of revisions.
> 
> And no drive space.
>

One of the key points of the implementation would have to be the ability
to delete old revisions without affecting the subsequent revisions. This
would allow people to keep the number of revisions down.

Also if each revision is in effect a patch on the last revision it could
cut down the disk space required to store them, or if that takes to long
to read a file then have every tenth version (0,10,20,30...not the tenth
versions I know but easier to read) as a full version of the file which
all future versions are changed off.

>> Furthermore, it turns out that often relationships between files are
>> more important.
> 
> And there are files that are not important at all.
> 
> Would you save every temp file?  To be meaningful you would need to know
> the process they were tied to in many cases.

I hadn't considered that but I did think that you could remove the old
revisions of a file at some configurable time after. This would allow
recovery in case of accidental deletion but should keep the disk space
usage down.

>> Thus, in the end it turns out that this stuff is better handled by
>> explicit version-control systems (which require explicit operations to
>> manage revisions) and atomic snapshots (for backup.)

Possibly but if I use it to manage my entire system (ie as a package
manager) then the system would likely explode if I tryed to update or
remove a key package whilst the system was running. With the kernel
involved then the process could be much smoother.

> ZFS is the cool new thing in that space.  Too bad the license makes it
> hard to incorporate it into the kernel.  (I am one of those people that
> believe that Linux should support EVERY file system, no matter how old
> or obscure.)

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