1
Fork 0
mirror of https://github.com/RGBCube/serenity synced 2025-07-27 11:47:46 +00:00

Base: Minor cleanup of a few man pages.

- Fix some typos and formatting.

- Add links to Mitigations from unveil / pledge.
This commit is contained in:
Brian Gianforcaro 2021-05-05 02:44:25 -07:00 committed by Andreas Kling
parent 325e491d34
commit 56fccf1667
3 changed files with 8 additions and 7 deletions

View file

@ -71,3 +71,4 @@ The `pledge()` system call was first introduced by OpenBSD. The implementation i
## See also
* [`unveil`(2)](unveil.md)
* [`Mitigations`(7)](../man7/Mitigations.md)

View file

@ -32,9 +32,9 @@ include the following characters:
A single `unveil()` call may specify multiple permission characters at once.
Subsequent `unveil()` calls may take away permissions from the ones allowed
earlier for the same file. Note that unveilng a path with any set of
earlier for the same file. Note that unveiling a path with any set of
permissions does not turn off the regular permission checks: access to a file
which the process has unvelied for itself, but has otherwise no appropriate
which the process has unveiled for itself, but has otherwise no appropriate
permissions for, will still be rejected. Unveiling a directory allows the
process to access any files inside the directory.
@ -58,7 +58,7 @@ the error.
* `EFAULT`: `path` and/or `permissions` are not null and not in readable
memory.
* `EPERM`: The veil is locked, or an attempt to add more permissions for an
already unvelied path was rejected.
already unveiled path was rejected.
* `EINVAL`: `path` is not an absolute path, or `permissions` are malformed.
All of the usual path resolution errors may also occur.
@ -90,3 +90,4 @@ unveil(nullptr, nullptr);
* [`pledge`(2)](pledge.md)
* [`chroot`(2)](chroot.md)
* [`Mitigations`(7)](../man7/Mitigations.md)