From mboxrd@z Thu Jan 1 00:00:00 1970 From: CaT Subject: Re: silent semantic changes with reiser4 Date: Sun, 29 Aug 2004 20:44:13 +1000 Message-ID: <20040829104413.GE871@zip.com.au> References: <20040828170515.GB24868@hh.idb.hist.no> <4131074D.7050209@namesys.com> <4131A3B2.30203@namesys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Linus Torvalds , Helge Hafting , Rik van Riel , Spam , Jamie Lokier , David Masover , Diego Calleja , christophe@saout.de, vda@port.imtp.ilyichevsk.odessa.ua, christer@weinigel.se, Andrew Morton , wichert@wiggy.net, jra@samba.org, hch@lst.de, linux-fsdevel@vger.kernel.org, Kernel Mailing List , flx@namesys.com, reiserfs-list@namesys.com, Al Viro Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com To: Hans Reiser Content-Disposition: inline In-Reply-To: <4131A3B2.30203@namesys.com> List-Id: linux-fsdevel.vger.kernel.org On Sun, Aug 29, 2004 at 02:36:50AM -0700, Hans Reiser wrote: > Linus Torvalds wrote: > >On Sat, 28 Aug 2004, Hans Reiser wrote: > >>I object to openat()..... > > > >Sound slike you object to O_XATTRS, not openat() itself. > > > >Realize that openat() works independently of any special streams, it's > >fundamentally a "look up name starting from this file" (rather than > >"starting from root" or "starting from cwd"). > > well, isn't that namespace fragmentation by definition? If you can't go > > cat filenameA/metas/permissions > filenameB/metas/permissions > > find / -exec cat {}/permissions \; | grep 4777 | wc -l My apologies if this question has been raised (and answered) elsewhere. I tried to keep up with the flamefest/discussion but it wasn't always possible. How would you do it for directories without making certain names illegal? ie taking the above you'd do: cat dirA/metas/permissions > dirB/metas/permissions But how does that distinguish an access to the metas for dirA and dirB from an access to a file called permissions within the metas directories of dirA and dirB? I think what Linus is trying to do, as far as naming, is create a consistant access scheme that works for all types of objects in the fs without making certain names illegal (and with plugins, those names are not even a fixed thing I believe). Feel free to correct me if I'm wrong, ofcourse. :) -- Red herrings strewn hither and yon.