From: Jeremy Allison <jra@samba.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "Andreas Grünbacher" <andreas.gruenbacher@gmail.com>,
"Miklos Szeredi" <miklos@szeredi.hu>,
"Seth Forshee" <seth.forshee@canonical.com>,
fuse-devel <fuse-devel@lists.sourceforge.net>,
"Linux FS-devel Mailing List" <linux-fsdevel@vger.kernel.org>,
"Michael j Theall" <mtheall@us.ibm.com>,
"Jean-Pierre André" <jean-pierre.andre@wanadoo.fr>,
"Nikolaus Rath" <Nikolaus@rath.org>,
"Andreas Gruenbacher" <agruenba@redhat.com>
Subject: Re: [PATCH 0/2] Support for posix ACLs in fuse
Date: Wed, 21 Sep 2016 12:00:17 -0700 [thread overview]
Message-ID: <20160921190017.GC2417@jeremy-ThinkPad-X1-Carbon-4th> (raw)
In-Reply-To: <87bmzhdu9a.fsf@x220.int.ebiederm.org>
On Wed, Sep 21, 2016 at 12:42:41PM -0500, Eric W. Biederman wrote:
>
> I certainly don't need any kind of ACLs for any kind of files I have
> ever dealt with in practice...
<SARCASM FILTER ON>
Oh well, if *you* don't need them then job done !
I don't need iSCSI device support on my home systems
either, can we remove that code as well please ?
</SARCASM FILTER OFF>
RichACLs (or their NFSv4 equivalent) are an essential
feature for Linux enterprise storage.
You might not need or use them, but there
is a great demand for this feature in enterprise
storage applications.
next prev parent reply other threads:[~2016-09-21 19:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 13:46 [PATCH 0/2] Support for posix ACLs in fuse Seth Forshee
2016-08-29 13:46 ` [PATCH 1/2] fuse: Use generic xattr ops Seth Forshee
2016-08-29 13:46 ` [PATCH 2/2] fuse: Add posix ACL support Seth Forshee
2016-09-07 3:32 ` [PATCH 0/2] Support for posix ACLs in fuse Nikolaus Rath
2016-09-07 12:32 ` Seth Forshee
2016-09-21 8:30 ` Miklos Szeredi
2016-09-21 12:25 ` Jean-Pierre André
2016-09-21 14:14 ` Miklos Szeredi
2016-09-21 20:50 ` [fuse-devel] " Michael Theall
2016-09-23 15:03 ` Miklos Szeredi
2016-09-21 13:41 ` Seth Forshee
2016-09-21 13:57 ` Miklos Szeredi
2016-09-28 19:34 ` Seth Forshee
2016-09-21 15:40 ` Eric W. Biederman
2016-09-21 17:24 ` Andreas Grünbacher
2016-09-21 17:42 ` Eric W. Biederman
2016-09-21 19:00 ` Jeremy Allison [this message]
2016-09-21 21:08 ` Andreas Grünbacher
2016-09-21 21:28 ` Andreas Grünbacher
2016-09-23 9:01 ` Miklos Szeredi
2016-09-23 9:15 ` Andreas Grünbacher
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=20160921190017.GC2417@jeremy-ThinkPad-X1-Carbon-4th \
--to=jra@samba.org \
--cc=Nikolaus@rath.org \
--cc=agruenba@redhat.com \
--cc=andreas.gruenbacher@gmail.com \
--cc=ebiederm@xmission.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=jean-pierre.andre@wanadoo.fr \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mtheall@us.ibm.com \
--cc=seth.forshee@canonical.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;
as well as URLs for NNTP newsgroup(s).