From mboxrd@z Thu Jan 1 00:00:00 1970 From: claus@xn--frber-gra.muc.de (=?ISO-8859-1?Q?Claus_F=E4rber?=) Subject: Re: silent semantic changes with reiser4 Date: 03 Sep 2004 15:23:00 +0200 Sender: linux-kernel-owner@vger.kernel.org Message-ID: <9G9vIAK3cDD@gmane.3247.org> References: <412E4999.1050504@sover.net> <9FuGrTY3cDD@3247.org> <1094051610.2777.20.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: reiserfs-list@namesys.com, linux-fsdevel@vger.kernel.org Return-path: To: linux-kernel@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Alan Cox schrieb/wrote: > On Maw, 2004-08-31 at 12:01, Claus F=E4rber wrote: >> A simple convention that meta data files start with, say ".$", would >> be enough. > POSIX/SuS don't permit this. The only "free" namespace is that starti= ng > "//" (and not as some desktops seem to think foo://). Remember always > send GUI desktop users files called http://read.me .. its fun 8) Well, the problem is that one does want the metadata to be in the ordinary namespace so that they are accessible with POSIX tools. (The current version of) POSIX does not have a "unified" namespace so a unified namespace can't be POSIX. I wonder if it makes sense to have an environment variable (maybe POSIXLY_CORRECT) to switch between POSIX and the unified namespace model. Of course, this would mean that all of this is handled in userspace (e.g. libc), whereas the kernel and filesystems export more "traditional" (e.g. with openat) interfaces. Accessing metadata as ordinary files would then work with other filesystems, too. Claus --=20 http://www.faerber.muc.de