public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Claudio Martins <ctpm@ist.utl.pt>
To: Sriram Ramkrishna <sriram.ramkrishna@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: extended acls..
Date: Tue, 19 May 2009 21:01:50 +0100	[thread overview]
Message-ID: <200905192101.50836.ctpm@ist.utl.pt> (raw)
In-Reply-To: <42ab06770905190950x5077edb0s3c55bd1c39ebeebe@mail.gmail.com>

On Tuesday 19 May 2009, Sriram Ramkrishna wrote:
>
> I'm curious if there is any plans to add extended acls ala AFS?  The
> reason I ask is that it seems in Linux we don't seem have moved off o=
f
> POSIX style acls and I think there is definitely at least from my
> perspective that having a richer set of acl would be needed.  For
> instance, we would need acls to deal with controlled countries if we
> are sharing data with them etc.  It is a big shame that there is no
> RFC for extended ACLs.
>

 Hi,

 As other people on this list have already said, the right implementati=
on=20
might not be through BTRFS. But IMHO if you are looking at extended ACL=
s=20
beyond what is already provided by many linux filesystems, you could lo=
ok at=20
NFS4 ACLs, which have semantics which should fit Linux and Posix better=
 than=20
AFS ACLs. Also, AFS ACLs being per directory and not per file, would be=
 less=20
flexible than NFS4's.

 Regards

Cl=C3=A1udio

--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2009-05-19 20:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-19 16:50 extended acls Sriram Ramkrishna
2009-05-19 18:06 ` Josef Bacik
2009-05-19 18:16   ` Sriram Ramkrishna
2009-05-19 18:21   ` Chris Mason
2009-05-19 19:08     ` jim owens
2009-05-19 20:01 ` Claudio Martins [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=200905192101.50836.ctpm@ist.utl.pt \
    --to=ctpm@ist.utl.pt \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sriram.ramkrishna@gmail.com \
    /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