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:	Tue, 19 Jun 2007 22:50:21 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Chris Snook <csnook@...hat.com>,
	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,
	alan <alan@...eserver.org>
Subject: Re: Versioning file system

On Tue, 19 Jun 2007 12:08:52 -0700
"H. Peter Anvin" <hpa@...or.com> 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 the character historically used for this purpose is
> ; (semicolon.)

Yes but tdskb:foo.mac[1013,1013,frob];4 is *not* elegant. POSIX is very
clear about what is acceptable as magic in a pathname, and the unix spec
even more so.  The NetApp approach recognizes two important things

1.	Old version access is the oddity not the norm
2.	Standards behaviour is important


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