On 2015-10-07 03:33, James Morris wrote:
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.On Tue, 6 Oct 2015, Andreas Gruenbacher wrote:On Tue, Oct 6, 2015 at 11:07 AM, Pavel Machek <pavel@xxxxxx> 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...
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
