From: Patrick Reader <_@pxeger.com>
To: linux-man@vger.kernel.org
Cc: alx.manpages@gmail.com
Subject: [patch] unshare.2: Add note about potential capabilities confusion
Date: Tue, 6 Sep 2022 09:01:25 +0000 [thread overview]
Message-ID: <0102018312086c29-13598a55-2c20-47eb-a288-a5bbe6f1caff-000000@eu-west-1.amazonses.com> (raw)
See https://bugzilla.kernel.org/show_bug.cgi?id=216215 for context.
I know nothing about groff formatting, so what I wrote here is based on
my inference from reading the existing source. If it's wrong, I apologise.
Signed-off-by: Patrick Reader <_@pxeger.com>
---
man/man2/unshare.2 | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/man/man2/unshare.2 b/man/man2/unshare.2
index e72464950..851129022 100644
--- a/man/man2/unshare.2
+++ b/man/man2/unshare.2
@@ -461,6 +461,16 @@ Such functionality may be added in the future, if
required.
.\"be incrementally added to unshare without affecting legacy
.\"applications using unshare.
.\"
+.PP
+Creating all kinds of namespace, except user namespaces, requires the
+.B CAP_SYS_ADMIN
+capability. However, since creating a user namespace automatically
confers a
+full set of capabilities, creating both a user namespace and any other type
+of namespace in the same
+.BR unshare ()
+call does not require the
+.B CAP_SYS_ADMIN
+capability in the original namespace.
.SH EXAMPLES
The program below provides a simple implementation of the
.BR unshare (1)
--
2.37.3
next reply other threads:[~2022-09-06 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 9:01 Patrick Reader [this message]
2022-09-06 11:50 ` [patch] unshare.2: Add note about potential capabilities confusion Alejandro Colomar
2022-09-06 11:58 ` Patrick Reader
2022-09-06 12:03 ` Alejandro Colomar
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=0102018312086c29-13598a55-2c20-47eb-a288-a5bbe6f1caff-000000@eu-west-1.amazonses.com \
--to=_@pxeger.com \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.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).