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: <46783D1C.5030408@redhat.com>
Date:	Tue, 19 Jun 2007 16:31:24 -0400
From:	Chris Snook <csnook@...hat.com>
To:	Jack Stone <jack@...keye.stone.uk.eu.org>
CC:	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

Jack Stone wrote:
> Chris Snook wrote:
>> 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.
>>> Using ; would defiantly break userspace
>>>
>>> Jack
>>>
>> I can escape the semicolon just fine in bash.  In fact, tab-completion
>> will do this automatically.  That's really a non-issue.  It just means
>> that anyone who wants to use this feature would have to know what
>> they're doing, which I believe is your goal, right?
> 
> I didn't realise this. Would ; break userspace if it was used as the
> delimiter?

I have no idea.  I've never written a file management utility or library, so I 
don't know if they handle those specially.

> This discussion may be academic as this design is looking less and less
> useful/workable.

Well, I'd argue that the most interesting part of this idea is how it works on 
the inside.  You can implement arbitrarily impractical interfaces to test it out 
as long as your code is modular enough to implement a community-agreeable 
interface once it's ready for a wider audience.

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