mirror of
https://github.com/systemd/systemd.git
synced 2024-11-23 18:23:32 +08:00
docs: fix a few typos
This commit is contained in:
parent
ecb1456d0c
commit
d8b67e05fb
@ -48,7 +48,7 @@ code should linked as few times as possible, ideally only once. Thus code that
|
||||
is used by "higher-level" components (e.g. our binaries which are linked to
|
||||
`libsystemd-shared-<nnn>.so`), would go to a subdirectory specific to that
|
||||
component if it is only used there. If the code is to be shared between
|
||||
components, it'd go to `src/shared/`. Shared code that that is used by multiple
|
||||
components, it'd go to `src/shared/`. Shared code that is used by multiple
|
||||
components that do not link to `libsystemd-shared-<nnn>.so` may live either in
|
||||
`src/libsystemd/`, `src/basic/`, or `src/fundamental/`. Any code that is used
|
||||
only for EFI goes under `src/boot/efi/`, and `src/fundamental/` if is shared
|
||||
|
@ -117,7 +117,7 @@ Specifically, the following mechanisms are in place:
|
||||
|
||||
4. The
|
||||
[`systemd-sysusers(8)`](https://www.freedesktop.org/software/systemd/man/systemd-sysusers.service.html)
|
||||
will component automatically populate `/etc/passwd` and `/etc/group` on
|
||||
component will automatically populate `/etc/passwd` and `/etc/group` on
|
||||
first boot with further necessary system users.
|
||||
|
||||
5. The
|
||||
|
@ -730,7 +730,7 @@ SPDX-License-Identifier: LGPL-2.1-or-later
|
||||
hard. Moreover, while we rely heavily on GitHub's project management
|
||||
infrastructure we'd like to keep everything that can reasonably be kept in
|
||||
the git repository itself in the git repository, so that we can theoretically
|
||||
move things elswhere with the least effort possible.
|
||||
move things elsewhere with the least effort possible.
|
||||
|
||||
- It's OK to reference GitHub PRs, GitHub issues and git commits from code
|
||||
comments. Cross-referencing code, issues, and documentation is a good thing.
|
||||
|
@ -442,5 +442,5 @@ hence a great place to store credentials to load on the system.
|
||||
## Conditionalizing Services
|
||||
|
||||
Sometimes it makes sense to conditionalize system services and invoke them only
|
||||
if the right system credential is passed to the system. use the
|
||||
if the right system credential is passed to the system. Use the
|
||||
`ConditionCredential=` and `AssertCredential=` unit file settings for that.
|
||||
|
@ -95,7 +95,7 @@ This command does the following:
|
||||
image, and looks for all included unit files.
|
||||
|
||||
2. It copies out all unit files with a suffix of `.service`, `.socket`,
|
||||
`.target`, `.timer` and `.path`. whose name begins with the image's name
|
||||
`.target`, `.timer` and `.path`, whose name begins with the image's name
|
||||
(with `.raw` removed), truncated at the first underscore if there is one.
|
||||
This prefix name generated from the image name must be followed by a ".",
|
||||
"-" or "@" character in the unit name. Or in other words, given the image
|
||||
|
Loading…
Reference in New Issue
Block a user