fsckd daemon for inter-fsckd communication
Global logic:
Add systemd-fsckd multiplexer which accepts multiple (via systemd-fsck's
/run/systemd/fsck.progress socket) fsck instances to connect to it and sends
progress report. systemd-fsckd then computes and writes to /dev/console the
number of devices currently being checked and the minimum fsck progress.
Plymouth and user interaction:
Forward the progress to plymouth and support canellation of in progress fsck.
Try to connect and send to plymouth (if running) some checked report progress,
using direct plymouth protocole.
Update message is the following:
fsckd:<num_devices>:<progress>:<string>
* num_devices corresponds to the current number of devices being checked (int)
* progress corresponds to the current minimum percentage of all devices being
checked (float, from 0 to 100)
* string is a translated message ready to be displayed by the plymouth theme
displaying the information above. It can be overridden by plymouth themes
supporting i18n.
Grab in fsckd plymouth watch key Control+C, and propagate this cancel request
to systemd-fsck which will terminate fsck.
Send a message to signal to user what key we are grabbing for fsck cancel.
Message is: fsckd-cancel-msg:<string>
Where string is a translated string ready to be displayed by the plymouth theme
indicating that Control+C can be used to cancel current checks. It can be
overridden (matching only fsckd-cancel-msg prefix) for themes supporting i18n.
Misc:
systemd-fsckd stops on idle when no fsck is connected.
Add man page explaining the plymouth theme protocol, usage of the daemon
as well as the socket activation part. Adapt existing fsck man page.
Note that fsckd had lived in the upstream tree for a while, but was removed.
More information at
http://lists.freedesktop.org/archives/systemd-devel/2015-April/030175.html
-
Gbp-Pq: Topic debian
Gbp-Pq: Name fsckd-daemon-for-inter-fsckd-communication.patch
test: skip test-path on Salsa CI
Salsa is the Debian git forge. In the package build environment test-path
always fails as we cannot set up cgroups and so the path unit fails to
start. Skip the test in that environment.
Unfortunately meson doesn't allow one to skip individual tests by name.
Origin: upstream, https://github.com/systemd/systemd/commit/
a0b0b670ab6caa119eef37bda0d70b7273a70568
Gbp-Pq: Name test-skip-test-path-on-Salsa-CI.patch
systemd (254.4-1) unstable; urgency=medium
[ Michael Biebl ]
* Fix installation of tzdata-legacy. Apply a version constraint to the
tzdata alternative. Specifically (<< 2023c-8), which is the version
tzdata was split. Otherwise tzdata-legacy is not considered, as tzdata
is installed by default. (Closes: #
1051760)
* Drop obsolete Breaks/Replaces and migration code for versions older
than oldstable
* Drop -f from update-rc.d udev remove
[ Luca Boccassi ]
* upstream-ci: run unit tests from installed location. (Closes: #
1051756)
* New upstream version 254.4. Fixes minor security issue in arm64
and riscv64 systemd-boot (EFI) with device tree blobs loading:
https://github.com/systemd/systemd/security/advisories/GHSA-6m6p-rjcq-334c
* Refresh patches
* Install factory-reset related units
[ Gioele Barabucci ]
* debian/udev.debian-udev.sysusers: Add Debian-specific sysusers for
udev
* d/udev.postinst: Do not use addgroup to add udev-related groups
* d/control: Remove adduser, it is no longer needed now that all
udev-related groups are generated via `sd-sysusers`.
[dgit import unpatched systemd 254.4-1]
projects / systemd.git / log