| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
- their names are prefixed with "journal_",
- make them not directly use global variables,
- simplifies the loop counter in find_boot_by_offset().
|
|
|
|
| |
To make journal entries always contain valid boot ID.
|
|
|
|
|
| |
The two callers of journal_file_append_entry_internal() always pass
non-NULL boot ID.
|
|
|
|
|
|
| |
journal_file_verify_header()
Then, we can drop the redundant check in journal_file_read_tail_timestamp().
|
| |
|
| |
|
| |
|
|\
| |
| | |
Small fixups for first boot
|
| |
| |
| |
| |
| | |
We use the phrase "unpopulated" in systemd.unit(5) too.
And "/etc/ is empty" is simply spurious.
|
| | |
|
|\ \
| | |
| | | |
resolved: minor varlink API tweaks
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
So, unfortunately oomd uses "io.system." rather than "io.systemd." as
prefix for its sockets. This is a mistake, and doesn't match the
Varlink interface naming or anything else in oomd.
hence, let's fix that.
Given that this is an internal protocol between PID1 and oomd let's
simply change this without retaining compat.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
O_CLOEXEC too
Let's move setting of O_NONBLOCK into varlink_server_listen_fd() and out
of varlink_server_create_listen_fd_socket(). The latter has two callers:
varlink_server_listen_fd() and varlink_server_listen_address(), which
guarantees O_CLOEXEC+O_NONBLOCK anyway, hence no neet to repeat the
logic.
|
|\ \ \
| | | |
| | | | |
string-util: make strgrowpad0() safer
|
| | | |
| | | |
| | | |
| | | | |
partition we want to write
|
| | |/
| |/|
| | |
| | |
| | | |
Let#s make sure we never shorten the allocation leaving an invalid
string (i.e. a memory allocation without a trailing NUL) around.
|
|\ \ \
| |/ /
|/| | |
dissect: fix man and bash-completion
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
- Add synopsis to `--discover` and `--validate` options.
- `-l` is for `--list`, not for `--mtree`.
|
| |/
|/| |
|
|\ \
| | |
| | | |
rename pcrphase binary to pcrextend
|
| | |
| | |
| | |
| | | |
out measurements
|
| | |
| | |
| | |
| | |
| | | |
Let's make the tool a tiny bit more generic by allowing the PCR index to
measure into to be configurable.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The tool initially just measured the boot phase, but was subsequently
extended to measure file system and machine IDs, too. At AllSystemsGo
there were request to add more, and make the tool generically
accessible.
Hence, let's rename the binary (but not the pcrphase services), to make
clear the tool is not just measureing the boot phase, but a lot of other
things too.
The tool is located in /usr/lib/ and still relatively new, hence let's
just rename the binary and be done with it, while keeping the unit names
stable.
While we are at it, also move the tool out of src/boot/ and into its own
src/pcrextend/ dir, since it's not really doing boot related stuff
anymore.
|
| |
| |
| |
| |
| |
| | |
To make debugging [0], hopefully, easier.
[0] https://github.com/systemd/systemd/issues/28504
|
|\ \
| |/
|/| |
man: a couple of small fixes
|
| |
| |
| |
| | |
This fixes sd_bus_error_add_map and man/sd_uid_get_state
|
|/
|
|
| |
It is defined later in the same file
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Latest mkosi sets $MKOSI_UID and $MKOSI_GID to the uid/gid of the
user running mkosi. Let's make use of this to run meson setup and
ninja as the user running mkosi, so that if we execute git as a
subprocess during meson setup, it doesn't complain about unsafe
directories. This also makes sure all the build artifacts are owned
on the host by the user running mkosi.
|
|
|
|
|
|
|
|
| |
Currently translated at 100.0% (227 of 227 strings)
Co-authored-by: 김인수 <simmon@nplob.com>
Translate-URL: https://translate.fedoraproject.org/projects/systemd/master/ko/
Translation: systemd/main
|
|
|
|
|
| |
(#29290)
To support multiple DHCP servers in a network.
|
|
|
|
|
|
| |
This commit adds hwdb entry for Miglia Technology Harmony Audio (HA02).
The device is an application of OXford Semiconductor FW970 and will be
supported by ALSA oxfw driver in future.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On slower/overloaded systems it may take a bit for the swtpm socket
to show up:
I: Started swtpm as PID 189419 with state dir /tmp/tmp.pWqUutuGUj
I: Configured emulated TPM2 device tpm-spapr
+ tee /var/tmp/systemd-test-TEST-70-TPM2_1/console.log
+ timeout --foreground 1200 /bin/qemu-system-ppc64le -smp 4 ...
qemu-system-ppc64le: -chardev socket,id=chrtpm,path=/tmp/tmp.pWqUutuGUj/sock: Failed to connect to '/tmp/tmp.pWqUutuGUj/sock': No such file or directory
E: qemu failed with exit code 1
Spotted regularly in the ppc64le cron job and in some Ubuntu CI/CentOS CI
pr runs [0].
[0] https://github.com/systemd/systemd/pull/29183#issuecomment-1721727927
|
|
|
|
|
|
| |
We can't do anything about them anyway, and most importantly this seems
to alleviate systemd/systemd-centos-ci#660, which should make the CIs
a bit less angry (at least until the issue is addressed properly).
|
|\
| |
| | |
sd-ndisc: make sd_ndisc return time values in usec
|
| |
| |
| |
| |
| | |
This also introduces sd_ndisc_router_get_lifetime_timestamp() and
friends that return timestamp rather than timespan.
|
| | |
|
|\ \
| | |
| | | |
sd-dhcp-client: preparation for later PR
|
| | |
| | |
| | |
| | |
| | | |
No functional change, just refactoring and preparation for later
commits.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
No functional change, just refactoring and preparation for later
commits.
|
|/ /
| |
| |
| |
| | |
No functional change, just refactoring and preparation for later
commits.
|
| |
| |
| |
| | |
Follow-up for efb6a76a2a097132087ee30720421136cba9e708
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I recently tried adding a FIDO2-Device as an unlocking method to the LUKS2 partition containing my Fedora install.
When trying to do this, I stumbled upon the here edited man files detailing how to do this.
I however could not unlock my partition with my FIDO2-Device after editing /etc/crypttab and rebooting.
As I found out after a while, I needed to regenerate / update my currently running / used initramfs (https://unix.stackexchange.com/a/705809).
This would have most likely solved itself for me with the next kernel update install (as far as I understand).
So I propose changing the files edited here to recommend or at least inform the user about this.
|