From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Akihiro Motoki <amotoki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: unshare.2: ffix
Date: Fri, 16 Jan 2015 07:42:01 +0100 [thread overview]
Message-ID: <54B8B2B9.6020301@gmail.com> (raw)
In-Reply-To: <CALhU9tmG39TE__PM6jvAd9wdh0pdy2tzNbGi71-deNyL_h_MyQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Thanks, Akihiro. Applied.
Cheers,
Michael
On 01/15/2015 06:21 PM, Akihiro Motoki wrote:
> diff --git a/man2/unshare.2 b/man2/unshare.2
> index 9b1d506..3bc1f9a 100644
> --- a/man2/unshare.2
> +++ b/man2/unshare.2
> @@ -311,7 +311,8 @@ does not have a mapping in the parent namespace (see
> .TP
> .BR EPERM " (since Linux 3.9)"
> .\" commit 3151527ee007b73a0ebd296010f1c0454a919c7d
> -.B CLONE_NEWUSER was specified in
> +.B CLONE_NEWUSER
> +was specified in
> .I flags
> and the caller is in a chroot environment
> .\" FIXME What is the rationale for this restriction?
>
>
--
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
prev parent reply other threads:[~2015-01-16 6:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 17:21 unshare.2: ffix Akihiro Motoki
[not found] ` <CALhU9tmG39TE__PM6jvAd9wdh0pdy2tzNbGi71-deNyL_h_MyQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-16 6:42 ` Michael Kerrisk (man-pages) [this message]
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=54B8B2B9.6020301@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=amotoki-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).