From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Eugene Syromyatnikov <evgsyr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH draft_keys 0/7] Minor edits
Date: Fri, 25 Nov 2016 11:01:27 +0100 [thread overview]
Message-ID: <287f9dec-aa76-51b8-24e2-ede1cc8f78c4@gmail.com> (raw)
In-Reply-To: <20161125010043.GA25181@obsidian>
Hi Eugene,
On 11/25/2016 02:00 AM, Eugene Syromyatnikov wrote:
> Hello.
>
> There are some minor edits to keyrings(7) (and one minor typo fix for
> keyctl(2)).
Thanks for this series!
> One additional idea: add_key(2) and request_key(2) have some duplication
> regarding special keyrings (as already noted in comments there),
(yes.)
> maybe
> add overview information regarding them (along with constant names)
> to the Keyrings section of the keyrings(7) and then reference it from
> add_key/request_key (with the notes regarding non-applicability of
> requestor keyring in add_key and such).
Yes, I'd wondered about doing something like that. But, I'm
balancing that against inconvenience to the reader, by forcing
them to look at another page. So far, it seems best to leave
things as they are, but I'm still thinking about it.
> Another thought is to document group keyring (that it is present since
> beginning but has never been implemented), since it has a constant
> definition and one may think (upon possible discovery in headers) that
> it is just some undocumented feature.
I've added a few words on this to keyrings(7).
Everything is now pushed to Git.
Cheers,
Michael
> Eugene Syromyatnikov (7):
> keyctl.2: tfix
> keyrings.7: minor clarification rearding storage method used in
> keyrings
> keyrings.7: spacing fix
> keyrings.7: minor clarification regarding decision whether to store
> big_key in tmpfs or not
> keyrings.7: tfix
> keyrings.7: tfix
> keyrings.7: information regarding pre-3.17 limits on
> root_maxbytes/root_maxkeys
>
> man2/keyctl.2 | 1 -
> man7/keyrings.7 | 20 ++++++++++++--------
> 2 files changed, 12 insertions(+), 9 deletions(-)
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-11-25 10:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 15:47 Revised keyrings(7) man page for review Michael Kerrisk
[not found] ` <51643019-bb42-4066-c824-c55b9e668ac6-ASgREoAs3yw@public.gmane.org>
2016-11-25 1:00 ` [PATCH draft_keys 0/7] Minor edits Eugene Syromyatnikov
2016-11-25 10:01 ` Michael Kerrisk (man-pages) [this message]
2016-11-25 1:00 ` [PATCH draft_keys 1/7] keyctl.2: tfix Eugene Syromyatnikov
2016-11-25 8:35 ` Michael Kerrisk (man-pages)
2016-11-25 1:00 ` [PATCH draft_keys 2/7] keyrings.7: minor clarification rearding storage method used in keyrings Eugene Syromyatnikov
2016-11-25 8:37 ` Michael Kerrisk (man-pages)
2016-11-25 1:01 ` [PATCH draft_keys 3/7] keyrings.7: spacing fix Eugene Syromyatnikov
2016-11-25 8:39 ` Michael Kerrisk (man-pages)
2016-11-25 1:01 ` [PATCH draft_keys 4/7] keyrings.7: minor clarification regarding decision whether to store big_key in tmpfs or not Eugene Syromyatnikov
2016-11-25 8:40 ` Michael Kerrisk (man-pages)
2016-11-25 1:01 ` [PATCH draft_keys 5/7] keyrings.7: tfix Eugene Syromyatnikov
2016-11-25 8:42 ` Michael Kerrisk (man-pages)
2016-11-25 1:01 ` [PATCH draft_keys 6/7] " Eugene Syromyatnikov
2016-11-25 8:43 ` Michael Kerrisk (man-pages)
2016-11-25 1:01 ` [PATCH draft_keys 7/7] keyrings.7: information regarding pre-3.17 limits on root_maxbytes/root_maxkeys Eugene Syromyatnikov
2016-11-25 8:54 ` Michael Kerrisk (man-pages)
2016-11-26 12:51 ` Revised keyrings(7) man page for review Michael Kerrisk (man-pages)
2016-12-13 11:35 ` David Howells
[not found] ` <25262.1481628931-S6HVgzuS8uM4Awkfq6JHfwNdhmdF6hFW@public.gmane.org>
2016-12-13 12:43 ` Michael Kerrisk (man-pages)
[not found] ` <9f32a79b-5795-bff4-b741-bf927a525149-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-12-13 12:57 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkh9JLN4P+Fu+yRCNo96E3VwjYLRquuaf43XRWeuC7gnNw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-12-13 13:38 ` David Howells
[not found] ` <26913.1481636296-S6HVgzuS8uM4Awkfq6JHfwNdhmdF6hFW@public.gmane.org>
2016-12-13 13:52 ` Michael Kerrisk (man-pages)
[not found] ` <a5615075-dd39-e206-cbce-385bed72473f-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-12-13 14:20 ` David Howells
2016-12-14 7:27 ` Michael Kerrisk (man-pages)
2016-12-13 13:31 ` David Howells
2016-12-13 13:41 ` Michael Kerrisk (man-pages)
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=287f9dec-aa76-51b8-24e2-ede1cc8f78c4@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=evgsyr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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).