From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Masover Subject: Re: Reiser4 and ACLs Date: Mon, 15 Aug 2005 18:24:48 -0500 Message-ID: <43012440.8020804@slaphack.com> References: <42FEC9F1.9040709@perkel.com> <20050814080812.GA22983@king.bitgnome.net> <42FF388F.3010506@perkel.com> <17151.17921.996376.693013@gargle.gargle.HOWL> <87k6in5dri.fsf@evinrude.uhoreg.ca> <17152.63727.435377.223362@thebsh.namesys.com> <1124138041.11626.4.camel@localhost> <17152.65201.525419.283987@gargle.gargle.HOWL> <43010157.1030107@perkel.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com In-Reply-To: <43010157.1030107@perkel.com> List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Marc Perkel Cc: reiserfs-list@namesys.com Marc Perkel wrote: > > > Nikita Danilov wrote: > >> >> Well, this song has been sung many times already. :-) Hans has strong >> opinion about xattr API (which, indeed, is not a paragon of design >> beauty by a large margin). >> >> > I'm new to this debate. What is his strong opinion? Well, I'll let him speak for himself, but I think it's basically this: xattrs suck, for reasons which are varied and irrelevant. When it's done, the sys_reiser4 api (and file-as-dir/metas/whatever) will be able to do everything xattrs did, only much better, faster, and more powerfully. So, it's more worth their time to work on other things, like: - kernel acceptance - repacker - crypto/compression - security ("views" or ACLs) Of course, if someone wanted to pay them for xattrs, and they didn't have another contract going, they'd probably support xattrs. But for now, it's probably up to us to add xattr support. Once it's added, these should do the same thing: openat ("some_attribute") open ("metas/some_attribute") // or maybe open ("metas/xattrs/some_attribute") Well, there's more to it than that, but the most important thing is, the xattrs should be a subset of the metas namespace.