ext_attr overlaps

[LA Walsh]

> -----Original Message-----
> From: Robert Watson [mailto:rwatson at FreeBSD.org]
> Sent: Thursday, January 11, 2001 9:17 AM
> To: LA Walsh
> Cc: linux-fsdevel at vger.kernel.org;
> linux-privs-discuss at lists.sourceforge.net; posix1e at cyrus.watson.org
> Subject: Re: ext_attr overlaps
>
>
>
> If you're referring to userland,
---
	Wasn't.  but...

> there are some useful things to keep in
> mind (these have come up on linux-fsdevel in the last few months).  First,
> from the application perspective, directly accessing labels with semantics
> (such as ACLs, capabilities, etc) should be done through well defined and
> portable APIs, such as POSIX.1e calls.
---
	Agreed.  This generates implications...
> This is particularly true, I
> believe, if the goal is to have a sufficiently abstracted ACL API that it
> can support different sets of semantics in the underlying file system
> (NFSv4, AFS, Coda, POSIX.1e, ...).  Presumably, in some file systems,
> these calls are mapped into general extended attributes (FFS, HPFS, ...),
> and others they're stored natively in the file system (AFS, Coda, ...).
---
	If ACL's need to be sufficiently abstracted to work with a variety
of underlying fs-specific implementations, should the same assumptions
be made for MAC and CAP implementations?  It sounds like the answer
would be yes -- that for ext2, use the ea-get/set, but it may be different
for other file types.

	Of course it seems the vfs layer is quite changed in 2.4, so that's
another set of variables to work with....:-|.

-l

To Unsubscribe: send mail to majordomo at cyrus.watson.org
with "unsubscribe posix1e" in the body of the message