As reported by Fossies.org.
to the kernel which will then upload it to the CPU. This should be distinct
from .initrd to guarantee right ordering. also, and maybe more importantly
support .microcode in PE add-ons, so that a microcode update can be shipped
- indepdendently of any kernel.
+ independently of any kernel.
* add clean mechanism concept for passing env/creds from initrd to host on
switch root, so that cloud-init and similar have a clean, sane method to pass
* open up creds for uses in generators, and document clearly that encrypted
creds are only supported if strictly tpm bound, but not when using the host
- secret (as that is only avilable if /var/ is around.
+ secret (as that is only available if /var/ is around.
* logind: when logging in, always take an fd to the home dir, to keep the dir
busy, so that autofs release can never happen. (this is generally a good
is the head of the journal, e.g. when this is called following
<function>sd_journal_seek_head()</function>, then this is equivalent to
<function>sd_journal_next()</function>, and the argument <varname>advanced</varname> will be ignored.
- Similary, if the current location is the tail of the journal, e.g. when this is called following
+ Similarly, if the current location is the tail of the journal, e.g. when this is called following
<function>sd_journal_seek_tail()</function>, then this is equivalent to
<function>sd_journal_previous()</function>, and <varname>advanced</varname> will be ignored. Otherwise,
this is equivalent to <function>sd_journal_next()</function> when <varname>advanced</varname> is
<title>Resource Pass-Through</title>
<para>Various runtime OS resources can passed from a system runtime to the next, through the userspace
- reboot operation. Specificially:</para>
+ reboot operation. Specifically:</para>
<itemizedlist>
<listitem><para>File descriptors placed in the file descriptor store of services that remain active
clock does not pause. When a calendar timer elapses while the system is sleeping it will not be acted
on immediately, but once the system is later resumed it will catch up and process all timers that
triggered while the system was sleeping. Note that if a calendar timer elapsed more than once while
- the system was continously sleeping the timer will only result in a single service activation. If
+ the system was continuously sleeping the timer will only result in a single service activation. If
<varname>WakeSystem=</varname> (see below) is enabled a calendar time event elapsing while the system
is suspended will cause the system to wake up (under the condition the system's hardware supports
time-triggered wake-up functionality).</para></listitem>
<para>Next, we can generate the certificate and keys:</para>
<programlisting># /usr/lib/systemd/ukify genkey --config=/etc/kernel/uki.conf
Writing SecureBoot private key to /etc/kernel/secure-boot.key.pem
-Writing SecureBoot certicate to /etc/kernel/secure-boot.cert.pem
+Writing SecureBoot certificate to /etc/kernel/secure-boot.cert.pem
Writing private key for PCR signing to /etc/kernel/pcr-initrd.key.pem
Writing public key for PCR signing to /etc/kernel/pcr-initrd.pub.pem
Writing private key for PCR signing to /etc/kernel/pcr-system.key.pem
t = (TimestampStyle) string_table_lookup(timestamp_style_table, ELEMENTSOF(timestamp_style_table), s);
if (t >= 0)
return t;
- if (STRPTR_IN_SET(s, "µs", "μs")) /* acccept both µ symbols in unicode, i.e. micro symbol + greek small letter mu. */
+ if (STRPTR_IN_SET(s, "µs", "μs")) /* accept both µ symbols in unicode, i.e. micro symbol + Greek small letter mu. */
return TIMESTAMP_US;
if (STRPTR_IN_SET(s, "µs+utc", "μs+utc"))
return TIMESTAMP_US_UTC;
/* So here's the deal: the creation/birth time (crtime/btime) of a file is a relatively newly supported concept
* on Linux (or more strictly speaking: a concept that only recently got supported in the API, it was
* implemented on various file systems on the lower level since a while, but never was accessible). However, we
- * needed a concept like that for vaccuuming algorithms and such, hence we emulated it via a user xattr for a
+ * needed a concept like that for vacuuming algorithms and such, hence we emulated it via a user xattr for a
* long time. Starting with Linux 4.11 there's statx() which exposes the timestamp to userspace for the first
- * time, where it is available. Thius function will read it, but it tries to keep some compatibility with older
+ * time, where it is available. This function will read it, but it tries to keep some compatibility with older
* systems: we try to read both the crtime/btime and the xattr, and then use whatever is older. After all the
* concept is useful for determining how "old" a file really is, and hence using the older of the two makes
* most sense. */
test_check_numbers_down(j, 9);
sd_journal_close(j);
- /* Seek to tail, skip to head in a more complext way, then iterate down. */
+ /* Seek to tail, skip to head in a more complex way, then iterate down. */
assert_ret(sd_journal_open_directory(&j, t, 0));
assert_ret(sd_journal_seek_tail(j));
assert_ret(sd_journal_next(j)); /* no-op */
assert_se(sd_event_default(&e) >= 0);
- /* Create an event source that will continously fire by creating a pipe whose write side is closed,
+ /* Create an event source that will continuously fire by creating a pipe whose write side is closed,
* and which hence will only see EOF and constant EPOLLHUP */
assert_se(pipe2(pfd, O_CLOEXEC) >= 0);
assert_se(sd_event_add_io(e, &s, pfd[0], EPOLLIN, hup_callback, &c) >= 0);
assert_se(sd_event_source_set_ratelimit(s, 5*USEC_PER_MINUTE, 5) >= 0);
pfd[0] = -EBADF;
- pfd[1] = safe_close(pfd[1]); /* Trigger continous EOF */
+ pfd[1] = safe_close(pfd[1]); /* Trigger continuous EOF */
for (;;) {
r = sd_event_prepare(e);
return error;
}
-/* A small structure we store inside the PAM session object, that allows us to resue bus connections but pins
+/* A small structure we store inside the PAM session object, that allows us to reuse bus connections but pins
* it to the process thoroughly. */
struct PamBusData {
sd_bus *bus;
}
typedef enum PathRelativeTo {
- /* Please make sure to folow the naming of the corresponding PartitionDesignator enum values,
+ /* Please make sure to follow the naming of the corresponding PartitionDesignator enum values,
* where this makes sense, like for the following three. */
PATH_RELATIVE_TO_ROOT,
PATH_RELATIVE_TO_ESP,
if (r < 0)
log_error_errno(r, "Failed to make subvolume: %m");
- r = write_string_file("/xxxtest/afile", "ljsadhfljasdkfhlkjdsfha", WRITE_STRING_FILE_CREATE);
+ r = write_string_file("/xxxtest/file", "ljsadhfljasdkfhlkjdsfha", WRITE_STRING_FILE_CREATE);
if (r < 0)
log_error_errno(r, "Failed to write file: %m");
/* Open /p/s/m file before we unmount everything (which might include /proc/) */
f = fopen("/proc/self/mountinfo", "re");
if (!f) {
- log_error_errno(errno, "Faile to open /proc/self/mountinfo: %m");
+ log_error_errno(errno, "Failed to open /proc/self/mountinfo: %m");
_exit(EXIT_FAILURE);
}
" --clean Clean up marked directories\n"
" --remove Remove marked files/directories\n"
" --boot Execute actions only safe at boot\n"
- " --graceful Quitely ignore unknown users or groups\n"
+ " --graceful Quietly ignore unknown users or groups\n"
" --prefix=PATH Only apply rules with the specified prefix\n"
" --exclude-prefix=PATH Ignore rules with the specified prefix\n"
" -E Ignore rules prefixed with /dev, /proc, /run, /sys\n"
}
} else {
/* The requested devlink does not exist, or the target device does not exist and the devlink
- * points to a non-existing device. Let's search the deivce that has the highest priority,
+ * points to a non-existing device. Let's search the device that has the highest priority,
* and update the devlink. */
;
}
print(f'Writing SecureBoot private key to {opts.sb_key}')
with temporary_umask(0o077):
opts.sb_key.write_bytes(key_pem)
- print(f'Writing SecureBoot certicate to {opts.sb_cert}')
+ print(f'Writing SecureBoot certificate to {opts.sb_cert}')
opts.sb_cert.write_bytes(cert_pem)
for priv_key, pub_key, _ in key_path_groups(opts):
print(f'{YELLOW}SKIP: {name}{RESET_ALL}')
total.skip += 1
elif ex.returncode == 127:
- print(f'{YELLOW}SKIP: {name} (no interpeter) {RESET_ALL}')
+ print(f'{YELLOW}SKIP: {name} (no interpreter) {RESET_ALL}')
total.skip += 1
else:
print(f'{RED}FAIL: {name}{RESET_ALL}')
test -w "/sys/fs/cgroup/system.slice/$unit/zzz/cgroup.max.depth"
fi
-# Check that the invoked process itsel is also in the subgroup
+# Check that the invoked process itself is also in the subgroup
unit="test-subgroup-$RANDOM.service"
systemd-run --wait \
--unit="$unit" \
# This is the first boot
systemd-notify --status="First Boot"
- # Let's upload an fd to the fdstore, so that we can verify fdstore passing works correcly
+ # Let's upload an fd to the fdstore, so that we can verify fdstore passing works correctly
T="/dev/shm/fdstore.$RANDOM"
echo "wuffwuff" >"$T"
systemd-notify --fd=3 --pid=parent 3<"$T"
projects / thirdparty / systemd.git / commitdiff
