Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263484AbUDZUkp (ORCPT ); Mon, 26 Apr 2004 16:40:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263529AbUDZUkp (ORCPT ); Mon, 26 Apr 2004 16:40:45 -0400 Received: from krusty.dt.e-technik.Uni-Dortmund.DE ([129.217.163.1]:61088 "EHLO mail.dt.e-technik.uni-dortmund.de") by vger.kernel.org with ESMTP id S263484AbUDZUkm (ORCPT ); Mon, 26 Apr 2004 16:40:42 -0400 Date: Mon, 26 Apr 2004 22:40:37 +0200 From: Matthias Andree To: linux-kernel@vger.kernel.org, reiserfs-list@namesys.com Subject: Re: I oppose Chris and Jeff's patch to add an unnecessary additional namespace to ReiserFS Message-ID: <20040426204037.GA21455@merlin.emma.line.org> Mail-Followup-To: linux-kernel@vger.kernel.org, reiserfs-list@namesys.com References: <1082750045.12989.199.camel@watt.suse.com> <408D3FEE.1030603@namesys.com> <1083000711.30344.44.camel@watt.suse.com> <408D51C4.7010803@namesys.com> <1083006783.30344.102.camel@watt.suse.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1083006783.30344.102.camel@watt.suse.com> User-Agent: Mutt/1.5.5.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1540 Lines: 35 On Mon, 26 Apr 2004, Chris Mason wrote: > I hope v4 does improve the xattr api, and I hope it manages to do so for > more then just reiser4. It is important that application writers are > able to code to a single interface and get coverage across all the major > linux filesystems. Interesting point, given that SuSE were early adopters of alternative file systems such as JFS, ReiserFS, and XFS (in lexicographical order rather than order of appearance). These have always diversified the semantics offered, not only in adding features that other systems didn't have, but also in omitting features the other file systems did have - chattr, for instance, or tail merging that confused boot loaders, for another. With respect to Hans's reasoning about name spaces, is there an official standard that mandates a particular API for the ACL stuff ("POSIX")? If so, the whole discussion is about getting out of the frying pan and into the fire. The traditional approach will then be standards compliant but be out-of-band and outside of the file system name space, the new approach will be outside of the standards, requiring application developers to produce a Linux and a POSIX version. Or am I barking up the wrong tree? -- Matthias Andree Encrypt your mail: my GnuPG key ID is 0x052E7D95 - 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/