Hi,
On Tue, Feb 20, 2001 at 03:51:18PM +0100, Andreas Gruenbacher wrote:
> >
> > This still seems to offer no way of solving the big problem I've been
> > trying to stress for months now: you have namespace problems *inside*
> > an ACL namespace.
>
> Yes. The proposal tries to address what's an extended attribute, not
> what's inside an extended attribute. Even that proved pretty complex.
> There is no mention of what's inside any namespace, or what's inside a
> value. It only says there are additional restrictions on the permissible
> values for some namespaces.
>
> I see a couple of your ideas fit perfectly in a "what's inside an extended
> attribute" specification, though you seem to believe they're more of a
> "what extra operations are in a namespace" issue.
We're going round in circles again. :-)
Why should the ACL API have to assume that the ACLs are in fact stored
inside EAs? It is perfectly valid for a filesystem to support ACLs
without supporting generic EAs.
Cheers,
Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]