Hi,
On Fri, Feb 23, 2001 at 04:07:13PM +0100, Andreas Gruenbacher wrote:
> On Fri, 23 Feb 2001, Stephen C. Tweedie wrote:
>
> In fact, I'm not entirely happy with the acl_posix namespace, and after
> thinking about it consider the previous classification (user, inode,
> trusted, system) better. (This is also what Robert Watson suggested.)
>
> The different system attributes (ACLs, CAPs, MAC labels, etc.) could then
> be identified by attribute name, e.g., "acl.posix.access",
> "acl.posix.default", "acl.afs", "cap", etc.
Fine by me: that's a different way of encoding the namespace but
ultimately still gives us the same flexibility.
> This is a little bit more clear semantically: All EA's in `system' have
> the semantics of being passed in/out as one chunk, and the kernel needs to
> check values, convert and dispatch, etc.
One last question on this: do we still want to bother with
test-and-set operations on these attributes? Given that we have cases
where it's not actually possible (NFS), I'm not sure that it's worth
the bother.
Cheers,
Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]