LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

capget.2: wfix: consistently use "VFS capabilities" 

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2017-11-07 20:58:01 +01:00
parent 6a65cff8dd
commit c0f82ec111
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
man2/capget.2
View File

@ -118,7 +118,7 @@ and
whereas 32-bit capabilities use only
.IR datap [0].
.PP
On kernels that support file capabilities (VFS capability support),
On kernels that support file capabilities (VFS capabilities support),
these system calls behave slightly differently.
This support was added as an option in Linux 2.6.24,
and became fixed (nonoptional) in Linux 2.6.33.
@ -129,20 +129,20 @@ calls, one can probe the capabilities of any process by specifying its
process ID with the
.I hdrp->pid
field value.
.SS With VFS capability support
VFS Capability support creates a file-attribute method for attaching
.SS With VFS capabilities support
VFS capabilities support creates a file-attribute method for attaching
capabilities to executables.
This privilege model obsoletes kernel support for one process
asynchronously setting the capabilities of another.
That is, on kernels that VFS capability support, when calling
That is, on kernels that have VFS capabilities support, when calling
.BR capset (),
the only permitted values for
.I hdrp->pid
are 0 or, equivalently, the value returned by
.BR gettid (2).
.\"
.SS Without VFS capability support
On older kernels that do not provide VFS capability support
.SS Without VFS capabilities support
On older kernels that do not provide VFS capabilities support
.BR capset ()
can, if the caller has the
.BR CAP_SETPCAP