[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46783939.7000308@hawkeye.stone.uk.eu.org>
Date: Tue, 19 Jun 2007 21:14:49 +0100
From: Jack Stone <jack@...keye.stone.uk.eu.org>
To: Chris Snook <csnook@...hat.com>
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
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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists