Re: [PATCH v9 00/43] Richacls

From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: James Morris <jmorris@namei.org>,
	Andreas Gruenbacher <agruenba@redhat.com>
Cc: Pavel Machek <pavel@ucw.cz>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	"Theodore Ts'o" <tytso@mit.edu>,
	Andreas Dilger <adilger.kernel@dilger.ca>,
	"J. Bruce Fields" <bfields@fieldses.org>,
	Jeff Layton <jlayton@poochiereds.net>,
	Trond Myklebust <trond.myklebust@primarydata.com>,
	Anna Schumaker <anna.schumaker@netapp.com>,
	linux-ext4@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-nfs@vger.kernel.org, linux-api@vger.kernel.org
Subject: Re: [PATCH v9 00/43] Richacls
Date: Wed, 7 Oct 2015 09:21:20 -0400	[thread overview]
Message-ID: <56151C50.9060902@gmail.com> (raw)
In-Reply-To: <alpine.LRH.2.20.1510071832320.20498@namei.org>

[-- Attachment #1: Type: text/plain, Size: 1366 bytes --]

On 2015-10-07 03:33, James Morris wrote:
> On Tue, 6 Oct 2015, Andreas Gruenbacher wrote:
>
>> On Tue, Oct 6, 2015 at 11:07 AM, Pavel Machek <pavel@ucw.cz> wrote:
>>> Should there be file in Documentation/ explaining how this works?
>>
>> There are plenty of comments in the code and in the patch descriptions
>> that describe how the code works. The user-space package has manual
>> pages that describe how to use richacls; this information would not be
>> accessible to users when put in Documentation/. Also, some background
>> information is available on http://www.bestbits.at/richacl/.
>
> Are many distros planning on enabling this?  I gather RH is...
>
I think a better question is "Are many distros planning on supporting 
this?".  Most distros probably won't enable this immediately, and many 
other than the enterprise ones are likely to put the choice on the 
system administrator.  I would expect that RHEL, OEL, and SLES (and by 
extension, Fedora, CentOS, and OpenSuSE) are likely to enable it, and 
Ubuntu might.  Gentoo will likely take the same approach as it does with 
xattrs and POSIX ACL's, namely that if you want them, you enable them 
yourself.  I would expect Arch to have support (probably within a week 
or two of this being merged), but not enable them by default, and I'd 
expect a similar policy from Debian.


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]