From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Andreas Gruenbacher <agruenba@redhat.com>
Cc: mtk.manpages@gmail.com, "J. Bruce Fields" <bfields@fieldses.org>,
linux-ext4@vger.kernel.org, xfs@oss.sgi.com,
lkml <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, 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: setrichacl(1) man page review comments
Date: Sun, 14 Feb 2016 22:29:09 +0100 [thread overview]
Message-ID: <56C0F1A5.9010109@gmail.com> (raw)
In-Reply-To: <56B7716F.6060404@gmail.com>
Hi Andreas,
Here's a few more comments on the latest setrichacl(1)
page that I pulled out of the git repo.
> .\"
> .\" RichACL Manual Pages
> .\"
> .\" Copyright (C) 2015,2016 Red Hat, Inc.
> .\" Written by Andreas Gruenbacher <agruenba@redhat.com>
> .\" This is free documentation; you can redistribute it and/or
> .\" modify it under the terms of the GNU General Public License as
> .\" published by the Free Software Foundation; either version 2 of
> .\" the License, or (at your option) any later version.
> .\"
> .\" The GNU General Public License's references to "object code"
> .\" and "executables" are to be interpreted as the output of any
> .\" document formatting or typesetting system, including
> .\" intermediate and printed output.
> .\"
> .\" This manual is distributed in the hope that it will be useful,
> .\" but WITHOUT ANY WARRANTY; without even the implied warranty of
> .\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> .\" GNU General Public License for more details.
> .\"
> .\" You should have received a copy of the GNU General Public
> .\" License along with this manual. If not, see
> .\" <http://www.gnu.org/licenses/>.
> .\"
> .TH SETRICHACL 7 2015-09-01 "Linux" "Rich Access Control Lists"
>
> .SH NAME
> setrichacl \- Set Rich Access Control Lists
>
> .SH SYNOPSIS
> .B setrichacl
> .RI [ option "]... [" file ]...
>
> .SH DESCRIPTION
> The
> .B setrichacl
> utility sets or modifies Rich Access Control Lists (RichACLs) of files and
> directories.
>
> The
> .B \-m
> and
> .B \-s
> options expect an ACL or parts of an ACL on the command line. The
> .B \-M
> and
> .B \-S
> options read an ACL or parts of an ACL from a file. In either case, the entry
> format is described in section
> .I TEXT FORM
.I Text form
> of the
> .BR richacl (7)
> manual page. The single-letter or long forms of flags and permissions can be
> mixed arbitrarily. Multiple entries are separated by whitespace, newlines or
s/newlines/newlines,/
(You already use the "Oxford comma" convention elsewhere, so be consistent.)
> commas.
>
> Note that the order of entries in a RichACL matters, and that reordering
s/matters/is significant/
> entries may change the permissions granted.
>
> The use of
> .B deny
> entries is discouraged. If
> .B deny
> entries are used, they should be placed ahead of
> .B allow
> entries for improved interoperability with Windows where possible.
>
> When the file masks are not specified, they are computed automatically.
>
> When the ACL to be set is simple enough that the traditional file permission
> bits can express the same permissions,
> .B setrichacl
> sets the file permission bits and removes the ACL. When
> .BR setrichacl 's
> counterpart utility,
> .BR getrichacl (1),
> is used on a file or directory that does not have a RichACL, it displays the
> access permissions defined by the file permission bits as an ACL. This means
> that for simple ACLs,
> .B getrichacl
> may display a slightly different ACL which is equivalent to the one that was
> set with
> .BR setrichacl .
>
> .SS Permissions
>
> Setting ACLs or changing the file permission bits is allowed to the file owner,
> to processes which have the
> .B write_acl
> permission, and to processes which have the
> .B CAP_FOWNER
> capability.
>
> .SH OPTIONS
> .TP
> \fB\-\-modify\fR \fIacl\fR, \fB\-m\fR \fIacl\fR
> Modify the ACL of \fIfile\fR by replacing existing entries with the entries in
> \fIacl\fR, and adding all new entries. When the permissions of an entry are
> empty, remove the entry.
> .TP
> \fB\-\-modify\-file\fR \fIacl_file\fR, \fB\-M\fR \fIacl_file\fR
> Identical to \fB\-\-modify\fR, but read the ACL from \fIacl_file\fR instead. If
> the file is \(lq\-\(rq, read from standard input.
> .TP
> \fB\-\-set\fR \fIacl\fR, \fB\-s\fR \fIacl\fR
> Set the ACL of \fIfile\fR to \fIacl\fR. Any previous ACL is replaced.
> ACL entries are separated by whitespace, newlines, or commas.
> .TP
> \fB\-\-set\-file\fR \fIacl_file\fR, \fB\-S\fR \fIacl_file\fR
> Identical to \fB\-\-set\fR, but read the ACL from \fIacl_file\fR instead. If
> the file is \(lq\-\(rq, read from standard input.
> .TP
> \fB\-\-remove\fR, \fB\-b\fR
> Remove all extended permissions and revert to the file permission bits only.
> .TP
> \fB\-\-version\fR, \fB\-v\fR
> Display the version of
> .B setrichacl
> and exit.
> .TP
> \fB\-\-help\fR, \fB\-h\fR
> Display command-line usage help text.
>
> .\" .SH EXAMPLES
>
> .SH AUTHOR
> Written by Andreas Grünbacher <agruenba@redhat.com>.
>
> Please send your bug reports, suggested features and comments to the above address.
>
> .SH CONFORMING TO
> Rich Access Control Lists are Linux-specific.
>
> .SH SEE ALSO
> .BR getrichacl (1),
> .BR richacl (7)
Cheers,
Michael
next prev parent reply other threads:[~2016-02-14 21:29 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) [this message]
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)
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=56C0F1A5.9010109@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).