Message-ID: <46783939.7000308@hawkeye.stone.uk.eu.org>
Date: Tue, 19 Jun 2007 21:14:49 +0100
From: Jack Stone <jack@hawkeye.stone.uk.eu.org>
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: Chris Snook <csnook@redhat.com>
CC: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
       akpm@linux-foundation.org, viro@zeniv.linux.org.uk,
       alan <alan@clueserver.org>
Subject: Re: Versioning file system
References: <46731169.2090002@hawkeye.stone.uk.eu.org> <4673182B.4090800@redhat.com> <46739E89.1080003@hawkeye.stone.uk.eu.org> <46781A5B.9090104@redhat.com> <467829C4.5020101@zytor.com> <46782AA5.2000108@hawkeye.stone.uk.eu.org> <46783847.1020205@redhat.com>
In-Reply-To: <46783847.1020205@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1258
Lines: 35

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?

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

Jack

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/