xfs
[Top] [All Lists]

Re: [NEWS] Extended attributes interface changes

To: Linux XFS Mailing List <linux-xfs@xxxxxxxxxxx>
Subject: Re: [NEWS] Extended attributes interface changes
From: Ethan Benson <erbenson@xxxxxxxxxx>
Date: Sun, 3 Feb 2002 00:31:05 -0900
In-reply-to: <20020203125739.B104828@xxxxxxxxxxxxxxxxxxxxxxxx>; from nathans@xxxxxxx on Sun, Feb 03, 2002 at 12:57:39PM +1100
Mail-copies-to: nobody
Mail-followup-to: Linux XFS Mailing List <linux-xfs@xxxxxxxxxxx>
References: <20020201101545.G88469@xxxxxxxxxxxxxxxxxxxxxxxx> <Pine.LNX.4.44.0202021151090.5765-100000@xxxxxxxxxxxxxxxxxxxxxxxxx> <20020201213849.Y14742@xxxxxxxxxxxxxxx> <"from erbenson"@alaska.net> <20020203125739.B104828@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
On Sun, Feb 03, 2002 at 12:57:39PM +1100, Nathan Scott wrote:
> 
> We will be moving to the acl.bestbits.at implementation of
> ACLs which uses the extended attributes interfaces directly
> for ACLs, rather than separate syscalls as we have currently
> in the XFS tree.
> 
> So, there will be no second change for ACL userspace, it will
> all be done in one big step.

ah i see, so there will be no acl syscalls in the kernel, all of that
will be handled entirly in the userspace libacl, which uses the xattr
API just added yes?

does that mean libacl will need to know about the on disk format for
ACL extended attributes for each filesystem it supports? 

-- 
Ethan Benson
http://www.alaska.net/~erbenson/

Attachment: pgpcxhvBGGUWK.pgp
Description: PGP signature

<Prev in Thread] Current Thread [Next in Thread>