linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Andreas Gruenbacher <agruenba@redhat.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
	linux-ext4 <linux-ext4@vger.kernel.org>,
	XFS Developers <xfs@oss.sgi.com>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	linux-cifs@vger.kernel.org, Linux API <linux-api@vger.kernel.org>,
	Dave Chinner <david@fromorbit.com>,
	Christoph Hellwig <hch@infradead.org>,
	Anna Schumaker <anna.schumaker@netapp.com>,
	Trond Myklebust <trond.myklebust@primarydata.com>,
	Jeff Layton <jlayton@poochiereds.net>,
	Andreas Dilger <adilger@dilger.ca>
Subject: Re: richacl(7) man page review comments
Date: Mon, 15 Feb 2016 15:15:27 +0100	[thread overview]
Message-ID: <CAKgNAki53C7bZyWFSQMD1ArCD9w2V9RH0MozCk99G1=PuUUy1g@mail.gmail.com> (raw)
In-Reply-To: <CAHc6FU69k2uRXjSSS+9K0cXzFs74DPsz6DDv8GN=hmh7RpPA-Q@mail.gmail.com>

On 15 February 2016 at 12:35, Andreas Gruenbacher <agruenba@redhat.com> wrote:
> On Mon, Feb 15, 2016 at 11:25 AM, Michael Kerrisk (man-pages)
> <mtk.manpages@gmail.com> wrote:
>> You're right. I was confusing with xattr(7). So, I think it might
>> make some sense to eventually move both of these into man-pages (for
>> richacl(7), at least, it's probably worth delaying this for a bit),
>> since  they're describing kernel-user-space interfaces.
>
> Well, the actual user-space interface is xattrs in both cases.

Yes, xattrs are the base of the framework, but I was using "interface"
in a very broad way: ACLs and RichACLs are exposing kernel-defined
policies and rules about file permissions to user space (much as say
chmod(2) and the file mode bits). That's why it seems to make some
sense to place those pages with the other pages that describe
kernel-user-spaces interfaces. Plus, they'd now and then get some
man-pages love :-).

>> I can see counter-arguments too, such as these pages are closely
>> related to the corresponding user-space libraries you maintain.
>> What do you think?
>
> I would keep the man-pages where they are right now, but I don't have
> a strong preference.

I'd be happy to see acl(5) and eventually richacl(7) in man pages, but
it's your call in the end, of course.

Cheers,

Michael

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

  reply	other threads:[~2016-02-15 14:15 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-07 16:28 RichACLs man-pages review Michael Kerrisk (man-pages)
2016-02-07 16:29 ` Michael Kerrisk (man-pages)
2016-02-07 16:30 ` getrichacl(1) man page review comments Michael Kerrisk (man-pages)
2016-02-07 18:16   ` Martin Steigerwald
2016-02-14 21:30   ` Michael Kerrisk (man-pages)
2016-02-07 16:31 ` setrichacl(1) " Michael Kerrisk (man-pages)
2016-02-14 21:29   ` Michael Kerrisk (man-pages)
2016-02-07 16:35 ` richacl(7) " Michael Kerrisk (man-pages)
2016-02-10 19:34   ` J. Bruce Fields
2016-02-12 22:25   ` Andreas Gruenbacher
2016-02-14 21:27     ` Michael Kerrisk (man-pages)
2016-02-14 23:12       ` Andreas Gruenbacher
2016-02-15 10:25         ` Michael Kerrisk (man-pages)
2016-02-15 11:35           ` Andreas Gruenbacher
2016-02-15 14:15             ` Michael Kerrisk (man-pages) [this message]
2016-02-14 21:31     ` Michael Kerrisk (man-pages)
2016-02-20 16:37       ` Andreas Gruenbacher
2016-02-21 21:01         ` Michael Kerrisk (man-pages)
2016-02-21 21:40         ` Michael Kerrisk (man-pages)
2016-02-22 14:46           ` Andreas Gruenbacher
2016-02-23 10:16             ` Michael Kerrisk (man-pages)
2016-02-23 10:28               ` Andreas Gruenbacher
2016-02-28 22:11               ` Andreas Gruenbacher
2016-02-23 10:58             ` Michael Kerrisk (man-pages)
2016-02-23 11:14               ` Andreas Gruenbacher
2016-02-23 15:09               ` Andreas Gruenbacher
2016-02-23 19:01                 ` Andreas Gruenbacher

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='CAKgNAki53C7bZyWFSQMD1ArCD9w2V9RH0MozCk99G1=PuUUy1g@mail.gmail.com' \
    --to=mtk.manpages@gmail.com \
    --cc=adilger@dilger.ca \
    --cc=agruenba@redhat.com \
    --cc=anna.schumaker@netapp.com \
    --cc=bfields@fieldses.org \
    --cc=david@fromorbit.com \
    --cc=hch@infradead.org \
    --cc=jlayton@poochiereds.net \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@primarydata.com \
    --cc=xfs@oss.sgi.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).