From: Sean Bartell <wingedtachikoma@gmail.com>
To: Wayne Pollock <pollock@acm.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Permissions model for btrfs?
Date: Thu, 9 Dec 2010 13:02:33 -0500 [thread overview]
Message-ID: <20101209180233.GA3153@flcl.lan> (raw)
In-Reply-To: <4D011367.70501@acm.org>
On Thu, Dec 09, 2010 at 12:35:35PM -0500, Wayne Pollock wrote:
> I looked though the wiki (and "searched" the archives) but
> don't see an answer. Will btrfs support old POSIX-style ACLs
> and permissions, or the new NFS/NT style ACLs like ZFS? From
> the patch I saw, it seems old POSIX ACLs and permissions, but
> I'd like to know for sure. (And maybe the FAQ on the wiki could
> address this?) If it is the older POSIC ACLs, is there any plan
> to support NFSv4 ACLs in the future?
Right now it supports POSIX ACLs. I don't know about future plans.
> On a related note, will btrfs support any ext4 attributes (via chattr)?
It currently supports AaDdiS.
prev parent reply other threads:[~2010-12-09 18:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 17:35 Permissions model for btrfs? Wayne Pollock
2010-12-09 18:02 ` Sean Bartell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101209180233.GA3153@flcl.lan \
--to=wingedtachikoma@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=pollock@acm.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).