diff --git a/docs/BOOT_LOADER_SPECIFICATION.md b/docs/BOOT_LOADER_SPECIFICATION.md index 6bb72e0faa..803ba5440f 100644 --- a/docs/BOOT_LOADER_SPECIFICATION.md +++ b/docs/BOOT_LOADER_SPECIFICATION.md @@ -47,7 +47,7 @@ functionality. Here's why we think that it is not enough for our uses: * The various EFI implementations implement the boot order/boot item logic to different levels. Some firmware implementations do not offer a boot menu at all and instead unconditionally follow the EFI boot order, booting the first item that is working. * If the firmware setup is used to reset all data usually all EFI boot entries are lost, making the system entirely unbootable, as the firmware setups generally do not offer a UI to define additional boot items. By placing the menu item information on disk, it is always available, regardless if the BIOS setup data is lost. -* Harddisk images should be moveable between machines and be bootable without requiring explicit EFI variables to be set. This also requires that the list of boot options is defined on disk, and not in EFI variables alone. +* Harddisk images should be movable between machines and be bootable without requiring explicit EFI variables to be set. This also requires that the list of boot options is defined on disk, and not in EFI variables alone. * EFI is not universal yet (especially on non-x86 platforms), this specification is useful both for EFI and non-EFI boot loaders. * Many EFI systems disable USB support during early boot to optimize boot times, thus making keyboard input unavailable in the EFI menu. It is thus useful if the OS UI has a standardized way to discover available boot options which can be booted to. diff --git a/docs/HOME_DIRECTORY.md b/docs/HOME_DIRECTORY.md index d82aca7065..a3eabb7e63 100644 --- a/docs/HOME_DIRECTORY.md +++ b/docs/HOME_DIRECTORY.md @@ -125,7 +125,7 @@ medium. (Moreover it allows to embed additional partitions later on, for example for allowing a multi-purpose USB stick that contains both a home directory and a generic storage volume.) -Rationale for including the encrypted user record in the the LUKS2 header: +Rationale for including the encrypted user record in the LUKS2 header: Linux kernel file system implementations are generally not robust towards maliciously formatted file systems; there's a good chance that file system images can be used as attack vectors, exploiting the kernel. Thus it is diff --git a/docs/INITRD_INTERFACE.md b/docs/INITRD_INTERFACE.md index 8985f2761c..e59bbcce15 100644 --- a/docs/INITRD_INTERFACE.md +++ b/docs/INITRD_INTERFACE.md @@ -36,7 +36,7 @@ interfaces are currently used by dracut and the ArchLinux initrds. optionally followed (in `argv[2]`, `argv[3]`, … systemd's original command line options, for example `--log-level=` and similar. -* Storage daemons run from the initrd should follow the the guide on [systemd +* Storage daemons run from the initrd should follow the guide on [systemd and Storage Daemons for the Root File System](https://systemd.io/ROOT_STORAGE_DAEMONS) to survive properly from the boot initrd all the way to the point where systemd jumps back into the initrd diff --git a/docs/RANDOM_SEEDS.md b/docs/RANDOM_SEEDS.md index e4b4a7a9cb..da3fe40baa 100644 --- a/docs/RANDOM_SEEDS.md +++ b/docs/RANDOM_SEEDS.md @@ -212,10 +212,10 @@ boot, in order to ensure the entropy pool is filled up quickly. random-seed`](https://www.freedesktop.org/software/systemd/man/bootctl.html#random-seed)) a seed file with an initial seed is placed in a file `/loader/random-seed` in the ESP. In addition, an identically sized randomized EFI variable called - the the 'system token' is set, which is written to the machine's firmware - NVRAM. During boot, when `systemd-boot` finds both the random seed file and - the system token they are combined and hashed with SHA256 (in counter mode, - to generate sufficient data), to generate a new random seed file to store in + the 'system token' is set, which is written to the machine's firmware NVRAM. + During boot, when `systemd-boot` finds both the random seed file and the + system token they are combined and hashed with SHA256 (in counter mode, to + generate sufficient data), to generate a new random seed file to store in the ESP as well as a random seed to pass to the OS kernel. The new random seed file for the ESP is then written to the ESP, ensuring this is completed before the OS is invoked. Very early during initialization PID 1 will read diff --git a/man/homectl.xml b/man/homectl.xml index 3a4c6e5f5b..c5d9630632 100644 --- a/man/homectl.xml +++ b/man/homectl.xml @@ -401,7 +401,7 @@ configures how much time has to pass after changing the password of the user until the password may be changed again. If the user tries to change their password before this time passes the attempt is refused. - configures how much time has to pass after the the password is changed until the password expires and + configures how much time has to pass after the password is changed until the password expires and needs to be changed again. After this time passes any attempts to log in may only proceed after the password is changed. specifies how much earlier than then the time configured with the user is warned at login to diff --git a/man/org.freedesktop.LogControl1.xml b/man/org.freedesktop.LogControl1.xml index 385e290312..d8ce392c87 100644 --- a/man/org.freedesktop.LogControl1.xml +++ b/man/org.freedesktop.LogControl1.xml @@ -83,7 +83,7 @@ node /org/freedesktop/LogControl1 { LogTarget describes the log target (mechanism). It should be one of console (log to the console or standard output), kmsg (log to the kernel ring buffer), - journal (log the the journal natively, see + journal (log to the journal natively, see systemd-journald.service8), syslog (log using the syslog3 call). diff --git a/man/sd_hwdb_get.xml b/man/sd_hwdb_get.xml index 1372f4d80c..dbaaf6292c 100644 --- a/man/sd_hwdb_get.xml +++ b/man/sd_hwdb_get.xml @@ -64,7 +64,7 @@ sd_hwdb_get() queries the hwdb object created earlier with sd_hwdb_new3 for entries matching the specified string modalias, and returns the value - corresponding to the the key key. The value is returned as a + corresponding to the key key. The value is returned as a NUL-terminated string in value. It must not be modified by the caller and is valid as long as a reference to hwdb is kept. When multiple patterns in the database match modalias, the one with the highest priority is diff --git a/man/standard-conf.xml b/man/standard-conf.xml index a58c76d85f..ee8cc7bc0a 100644 --- a/man/standard-conf.xml +++ b/man/standard-conf.xml @@ -13,7 +13,7 @@ Configuration files are read from directories in /etc/, /run/, /usr/local/lib/, and /usr/lib/, in - order of precedence, as listed in the SYNOPSIS section above. Files must have the the + order of precedence, as listed in the SYNOPSIS section above. Files must have the .conf extension. Files in /etc/ override files with the same name in /run/, /usr/local/lib/, and /usr/lib/. Files in /run/ override files with the same name diff --git a/man/systemd.service.xml b/man/systemd.service.xml index 61484d530c..87929da81a 100644 --- a/man/systemd.service.xml +++ b/man/systemd.service.xml @@ -884,7 +884,7 @@ project='man-pages'>signal7 for a list of signal names. - Note that this setting does not change the the mapping between numeric exit statuses and their + Note that this setting does not change the mapping between numeric exit statuses and their names, i.e. regardless how this setting is used 0 will still be mapped to SUCCESS (and thus typically shown as 0/SUCCESS in tool outputs) and 1 to FAILURE (and thus typically shown as 1/FAILURE), and so on. It diff --git a/man/userdbctl.xml b/man/userdbctl.xml index 606ce673b5..e10f055222 100644 --- a/man/userdbctl.xml +++ b/man/userdbctl.xml @@ -218,7 +218,7 @@ Note that userdbctl has internal support for NSS-based lookups too. This means that if neither io.systemd.Multiplexer nor - io.systemd.NameSeviceSwitch are running look-ups into the the basic user/group + io.systemd.NameSeviceSwitch are running look-ups into the basic user/group databases will still work. diff --git a/src/core/bpf-firewall.c b/src/core/bpf-firewall.c index 2ec274df01..bceb049b58 100644 --- a/src/core/bpf-firewall.c +++ b/src/core/bpf-firewall.c @@ -544,7 +544,7 @@ int bpf_firewall_compile(Unit *u) { "BPF_F_ALLOW_MULTI is not supported on this manager, not doing BPF firewall on slice units."); /* Note that when we compile a new firewall we first flush out the access maps and the BPF programs themselves, - * but we reuse the the accounting maps. That way the firewall in effect always maps to the actual + * but we reuse the accounting maps. That way the firewall in effect always maps to the actual * configuration, but we don't flush out the accounting unnecessarily */ u->ip_bpf_ingress = bpf_program_unref(u->ip_bpf_ingress); diff --git a/src/core/execute.c b/src/core/execute.c index 4bee1b1966..078aa14418 100644 --- a/src/core/execute.c +++ b/src/core/execute.c @@ -2855,7 +2855,7 @@ static int setup_keyring( } out: - /* Revert back uid & gid for the the last time, and exit */ + /* Revert back uid & gid for the last time, and exit */ /* no extra logging, as only the first already reported error matters */ if (getuid() != saved_uid) (void) setreuid(saved_uid, -1); diff --git a/src/core/namespace.c b/src/core/namespace.c index 785a469478..93e077ce6f 100644 --- a/src/core/namespace.c +++ b/src/core/namespace.c @@ -747,7 +747,7 @@ static int mount_private_dev(MountEntry *m) { NULSTR_FOREACH(d, devnodes) { r = clone_device_node(d, temporary_mount, &can_mknod); - /* ENXIO means the the *source* is not a device file, skip creation in that case */ + /* ENXIO means the *source* is not a device file, skip creation in that case */ if (r < 0 && r != -ENXIO) goto fail; } diff --git a/src/home/pam_systemd_home.c b/src/home/pam_systemd_home.c index 34dfd134fc..dcf26ddaf5 100644 --- a/src/home/pam_systemd_home.c +++ b/src/home/pam_systemd_home.c @@ -499,7 +499,7 @@ static int acquire_home( return r; /* Implement our own retry loop here instead of relying on the PAM client's one. That's because it - * might happen that the the record we stored on the host does not match the encryption password of + * might happen that the record we stored on the host does not match the encryption password of * the LUKS image in case the image was used in a different system where the password was * changed. In that case it will happen that the LUKS password and the host password are * different, and we handle that by collecting and passing multiple passwords in that case. Hence we diff --git a/src/home/user-record-util.c b/src/home/user-record-util.c index 8f51f8d6e8..0881d1472c 100644 --- a/src/home/user-record-util.c +++ b/src/home/user-record-util.c @@ -172,7 +172,7 @@ int user_record_reconcile( * -REMCHG: identity records are not about the same user * -ESTALE: embedded identity record is equally new or newer than supplied record * - * Return the new record to use, which is either the the embedded record updated with the host + * Return the new record to use, which is either the embedded record updated with the host * binding or the host record. In both cases the secret data is stripped. */ assert(host); diff --git a/src/shared/varlink.c b/src/shared/varlink.c index 1f4d5a614c..be3559dc10 100644 --- a/src/shared/varlink.c +++ b/src/shared/varlink.c @@ -387,7 +387,7 @@ DEFINE_TRIVIAL_REF_UNREF_FUNC(Varlink, varlink, varlink_destroy); static int varlink_test_disconnect(Varlink *v) { assert(v); - /* Tests whether we the the connection has been terminated. We are careful to not stop processing it + /* Tests whether we the connection has been terminated. We are careful to not stop processing it * prematurely, since we want to handle half-open connections as well as possible and want to flush * out and read data before we close down if we can. */