On Thu, 26 Oct 2000, Ragnar Kj�rstad wrote:
> I think each system attribute will need it's own API;
> * A different API is probably better suitable for the user
> this can of course be handled in libc, but in some cases
> * different parts of the EA have different security policies
That's supported by system EA handlers. Two examples have already been
implemented: ACLs and Capabilities. Both require certain permissions, and
also restrict the permissible values. However, both have similar update
semantics: atomic replacement. That's why they work well as extended
attributes.
> If I understand Andreas correctly, his intention is to store _all_ ACL
> data in one EA. The ACL interface will update this one EA with new data;
> handling all the ordering and so on. As far as the filesystem is
> concerned, the "$ACL" is just another chunk of data it needs to store -
> it has no knowledge about what it is.
That's if the filesystem actually uses an EA to store the ACL. It may well
provide another mechanism, in which case EAs just provide the
interface.
Andreas.
------------------------------------------------------------------------
Andreas Gruenbacher, [EMAIL PROTECTED]
Contact information: http://www.bestbits.at/~ag/
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]
