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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 20 Jun 2007 10:34:53 +0200
From:	Bernd Petrovitsch <bernd@...mix.at>
To:	Jack Stone <jack@...keye.stone.uk.eu.org>
Cc:	"H. Peter Anvin" <hpa@...or.com>, Chris Snook <csnook@...hat.com>,
	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, 2007-06-19 at 20:12 +0100, 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 a
> >> special character.
> > 
> > Not to mention that the character historically used for this purpose is
> > ; (semicolon.)
> 
> But that would cause havoc with shells which use ; to seperate commands.

Then the user has to quote the ;. BTW `find` use a lone ';' since ages
to terminate it's '-exec' thingy.

> Using ; would defiantly break userspace

Only for buggy written shell scripts/commands. Who cares?

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services


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