| To: | Greg Freemyer <freemyer-ml@xxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: rdiff-backup / EAs / ACLs |
| From: | Nathan Scott <nathans@xxxxxxx> |
| Date: | Wed, 20 Aug 2003 08:24:52 +1000 |
| Cc: | linux-xfs@xxxxxxxxxxx, acl-devel@xxxxxxxxxxx |
| In-reply-to: | <20030819031858.GE940@frodo> |
| References: | <1061244256.29493.72.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20030819031858.GE940@frodo> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.3i |
On Tue, Aug 19, 2003 at 09:46:11 -0400, Greg Freemyer wrote:
> On Mon, 2003-08-18 at 23:18, Nathan Scott wrote:
> > On Mon, Aug 18, 2003 at 06:04:17 -0400, Greg Freemyer wrote:
> > >
> > > My understanding of xfs acls is that they are implemented via EAs.
> > > right?
> >
> > Yes, although libacl hides the user/kernel interface and
> > presents a (draft-POSIX-standard-compliant) ACL interface
> > to users which isn't aware of extended attributes.
>
> Does libattr allow access to ACLs, or from userland are EAs and ACLs
> truly distinct?
Yes, libattr sees system.{posix_acl_access,system.posix_acl_default}
as raw binary data, which I guess is all you need. libacl will let
you manipulate these as text also if you need that.
cheers.
--
Nathan
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | TAKE - Cleanups from Alexander Kabaev, Russell Cattelan |
|---|---|
| Next by Date: | Re: Problem regarding XFS allocation group, Nathan Scott |
| Previous by Thread: | Re: rdiff-backup / EAs / ACLs, Greg Freemyer |
| Next by Thread: | TAKE - xfsprogs, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |