diff options
| author | Karel Zak | 2016-03-14 16:15:04 +0100 |
|---|---|---|
| committer | Karel Zak | 2016-03-14 16:15:04 +0100 |
| commit | 79d8593fd76e6b3d2fb10c89c47dde55b5138487 (patch) | |
| tree | c1cdcd16eef9df109942067afd2380c5e0a32940 /sys-utils/unshare.1 | |
| parent | unshare: fix incomplete sentence in man page (diff) | |
| download | kernel-qcow2-util-linux-79d8593fd76e6b3d2fb10c89c47dde55b5138487.tar.gz kernel-qcow2-util-linux-79d8593fd76e6b3d2fb10c89c47dde55b5138487.tar.xz kernel-qcow2-util-linux-79d8593fd76e6b3d2fb10c89c47dde55b5138487.zip | |
unshare: tiny change
Signed-off-by: Karel Zak <kzak@redhat.com>
Diffstat (limited to 'sys-utils/unshare.1')
| -rw-r--r-- | sys-utils/unshare.1 | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/sys-utils/unshare.1 b/sys-utils/unshare.1 index c62d24c69..ba47c6733 100644 --- a/sys-utils/unshare.1 +++ b/sys-utils/unshare.1 @@ -118,7 +118,7 @@ syscall in user namespaces. .BR setgroups (2) is only callable with CAP_SETGID and CAP_SETGID in a user -namespace. Linux kernel since 3.19 does not give you permission to call setgroups(2) +namespace. Linux kernel (since 3.19) does not give you permission to call setgroups(2) until after GID map has been set. The GID map is writable by root when .BR setgroups (2) is enabled and the GID map becomes writable by unprivileged processes when |