mirror of
https://github.com/RGBCube/serenity
synced 2025-07-25 22:27:35 +00:00
Everywhere: Remove unnecessary whitespace at the end of some lines.
This commit is contained in:
parent
6749ba3477
commit
1f81bc6879
32 changed files with 76 additions and 76 deletions
|
@ -58,5 +58,5 @@ $ syscall exit 2
|
|||
|
||||
## History
|
||||
|
||||
This is a direct port of a utility with the same name originated from the Plan 9 operating system.
|
||||
This is a direct port of a utility with the same name originated from the Plan 9 operating system.
|
||||
|
||||
|
|
|
@ -10,7 +10,7 @@ $ unzip file.zip
|
|||
|
||||
## Description
|
||||
|
||||
unzip will extract files from a zip archive to the current directory.
|
||||
unzip will extract files from a zip archive to the current directory.
|
||||
|
||||
The program is compatible with the PKZIP file format specification.
|
||||
|
||||
|
|
|
@ -12,7 +12,7 @@ int set_process_name(const char* name, size_t name_length);
|
|||
|
||||
## Description
|
||||
|
||||
`set_process_name()` changes the name of the calling process to the string `name` with length `name_length`.
|
||||
`set_process_name()` changes the name of the calling process to the string `name` with length `name_length`.
|
||||
|
||||
## Pledge
|
||||
|
||||
|
|
|
@ -29,7 +29,7 @@ A `posix_spawn_file_actions_t` object is allocated on the stack but starts in an
|
|||
|
||||
`posix_spawn_file_actions_destroy()` frees up resources used by a valid `posix_spawn_file_actions_t` object and puts it into an undefined state. It has to be called after a `posix_spawn_file_actions_t` object is no longer needed.
|
||||
|
||||
It is valid to alternatingly call `posix_spawn_file_actions_init()` and `posix_spawn_file_actions_destroy()` on the same object,
|
||||
It is valid to alternatingly call `posix_spawn_file_actions_init()` and `posix_spawn_file_actions_destroy()` on the same object,
|
||||
|
||||
`posix_spawn_file_actions_addchdir()` and `posix_spawn_file_actions_addfchdir()` make `posix_spawn()` change the current working directory before spawning a process, like `chdir` and `fchdir` would.. The current working directory affects the spawned child process, but also relative paths passed to later `posix_spawn_file_actions_add(f)chdir()` and `posix_spawn_file_actions_addopen()`, and relative paths passed to `posix_spawn()` for the executable path.
|
||||
|
||||
|
|
|
@ -44,7 +44,7 @@ A `posix_spawnattr_t` object is allocated on the stack but starts in an undefine
|
|||
|
||||
`posix_spawnattr_destroy()` frees up resources used by a valid `posix_spawn_file_actions_t` object and puts it into an undefined state. It has to be called after a `posix_spawnattr_t` object is no longer needed.
|
||||
|
||||
It is valid to alternatingly call `posix_spawnattr_init()` and `posix_spawnattr_destroy()` on the same object,
|
||||
It is valid to alternatingly call `posix_spawnattr_init()` and `posix_spawnattr_destroy()` on the same object,
|
||||
|
||||
`posix_spawnattr_setflags()` configures which attributes of the new child process `posix_spawn()` will set. It receives a bitmask that can contain:
|
||||
|
||||
|
|
|
@ -8,7 +8,7 @@ mem - physical system memory
|
|||
the physical memory.
|
||||
|
||||
Trying to [`mmap`(2)](../mmap.md) a physical range results either with success,
|
||||
or with an error. When invoking [`mmap`(2)](../mmap.md) on bad memory range,
|
||||
or with an error. When invoking [`mmap`(2)](../mmap.md) on bad memory range,
|
||||
the kernel will write a message about it to the kernel log.
|
||||
|
||||
By default, the kernel limits the areas which can be accessed. The allowed areas
|
||||
|
|
|
@ -148,7 +148,7 @@ Commands can be either calls to Shell builtins, or external programs.
|
|||
The commands can be composed into semantic elements, producing composite commands:
|
||||
|
||||
### Sequences
|
||||
A sequence of commands, executed serially independent of each other: `Commanad ; Command ; Command ...`
|
||||
A sequence of commands, executed serially independent of each other: `Commanad ; Command ; Command ...`
|
||||
|
||||
It should be noted that a newline (`\\n`) can be substituted for the semicolon (`;`).
|
||||
|
||||
|
|
|
@ -90,7 +90,7 @@ It was first enabled in the following [commit](https://github.com/SerenityOS/ser
|
|||
|
||||
```
|
||||
commit 823186031d9250217f9a51829d34a96b74113334
|
||||
Author Andreas Kling <kling@serenityos.org>
|
||||
Author Andreas Kling <kling@serenityos.org>
|
||||
Date: Tue Feb 2 19:56:11 2021 +0100
|
||||
|
||||
Kernel: Add a way to specify which memory regions can make syscalls
|
||||
|
@ -201,7 +201,7 @@ Everywhere: Build with -fstack-clash-protection
|
|||
|
||||
The GCC compiler provides a few variants of the `-fstack-protector` option mitigation.
|
||||
This family of flags enables [buffer overflow protection](https://en.wikipedia.org/wiki/Buffer_overflow_protection)
|
||||
to mitigate [stack-smashing attacks](https://en.wikipedia.org/wiki/Stack_buffer_overflow).
|
||||
to mitigate [stack-smashing attacks](https://en.wikipedia.org/wiki/Stack_buffer_overflow).
|
||||
|
||||
The compiler implements the mitigation by storing a canary value randomized on program startup into the preamble of all
|
||||
functions. Code is then generated to validate that stack canary on function return and crash if the value has been changed
|
||||
|
@ -217,7 +217,7 @@ Date: Fri Dec 20 20:51:50 2019 +0100
|
|||
Kernel+LibC: Build with basic -fstack-protector support
|
||||
```
|
||||
|
||||
It was later re-enabled and refined to `-fstack-protector-strong` in the following commits:
|
||||
It was later re-enabled and refined to `-fstack-protector-strong` in the following commits:
|
||||
```
|
||||
|
||||
commit fd08c93ef57f71360d74b035214c71d7f7bfc5b8
|
||||
|
|
|
@ -21,7 +21,7 @@ This program must be run as root.
|
|||
* `-u`, `--uid` _uid_: The user identifier for the new user. If not specified, an unused UID above `1000` will be auto-generated.
|
||||
* `-g`, `--gid` _gid_: The group identifier for the new user. If not specified, it will default to 100 (the **users** group).
|
||||
* `-p`, `--password` _password_: The encrypted password for the new user. If not specified, it will default to blank.
|
||||
* `-s`, `--shell` _path-to-shell_: The shell binary for this login. The default is `/bin/Shell`.
|
||||
* `-s`, `--shell` _path-to-shell_: The shell binary for this login. The default is `/bin/Shell`.
|
||||
* `-m`, `--create-home`: Create the specified home directory for this new user.
|
||||
* `-d`, `--home-dir` _path_: Set the home directory for this user to path. By default, this is `/home/username`, where `username` is the value of login.
|
||||
* `-n`, `--gecos` _general-info_: GECOS information about this login. See [Wikipedia](https://en.wikipedia.org/wiki/Gecos_field) for more information.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue