| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| debian/Bring-tmpfiles.d-tmp.conf-in-line-with-Debian-defaul.patch | Bring tmpfiles.d/tmp.conf in line with Debian defaults | Tollef Fog Heen <tfheen@err.no> | no | 2012-06-05 | ||
| debian/Make-run-lock-tmpfs-an-API-fs.patch | Make /run/lock tmpfs an API fs The /run/lock directory is world-writable in Debian due to historic reasons. To avoid user processes filling up /run, we mount a separate tmpfs for /run/lock. As this directory needs to be available during early boot, we make it an API fs. Drop it from tmpfiles.d/legacy.conf to not clobber the permissions. |
Michael Biebl <biebl@debian.org> | no | 2014-09-05 | ||
| debian/fsckd-daemon-for-inter-fsckd-communication.patch | 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 - |
Didier Roche <didrocks@ubuntu.com> | no | 2015-05-22 | ||
| debian/Skip-filesystem-check-if-already-done-by-the-initram.patch | Skip filesystem check if already done by the initramfs Newer versions of initramfs-tools already fsck and mount / and /usr in the initramfs. Skip the filesystem check in this case. Based on a previous patch by Michael Biebl <biebl@debian.org>. |
Nis Martensen <nis.martensen@web.de> | no | 2016-01-19 | ||
| debian/Revert-core-set-RLIMIT_CORE-to-unlimited-by-default.patch | Revert "core: set RLIMIT_CORE to unlimited by default" Partially revert commit 15a900327ab as this completely breaks core dumps without systemd-coredump. It's also contradicting core(8), and it's not systemd's place to redefine the kernel definitions of core files. Commit bdfd7b2c now honours the process' RLIMIT_CORE for systemd-coredump. This isn't what RLIMIT_CORE is supposed to do (it limits the size of the core *file*, but the kernel deliberately ignores it for piping), so set a static 2^63 core size limit for systemd-coredump to go back to the previous behaviour (otherwise the change above would break systemd-coredump). |
Martin Pitt <martin.pitt@ubuntu.com> | no | debian | 2016-02-27 | |
| debian/systemctl-do-not-shutdown-immediately-on-scheduled-shutdo.patch | systemctl: do not shutdown immediately on scheduled shutdown When, for whatever reason, a scheduled shutdown fails to be set, systemd will proceed with immediate shutdown without allowing the user to react. This is counterintuitive because when a scheduled shutdown is issued, it means the user wants to shutdown at a specified time in the future, not immediately. This patch prevents the immediate shutdown and informs the user that no action will be taken. |
Ioanna Alifieraki <ioanna-maria.alifieraki@canonical.com> | no | 2020-12-17 | ||
| debian/Downgrade-a-couple-of-warnings-to-debug.patch | Downgrade a couple of warnings to debug If a package still ships only a SysV init script or if a service file or tmpfile uses /var/run, downgrade those messages to debug. We can use lintian to detect those issues. For service files and tmpfiles in /etc, keep the warning, as those files are typically added locally and aren't checked by lintian. |
Michael Biebl <biebl@debian.org> | no | 2021-02-16 | ||
| debian/Skip-flaky-test_resolved_domain_restricted_dns-in-network.patch | Skip flaky test_resolved_domain_restricted_dns in networkd-test.py This test is part of DnsmasqClientTest and does not work reliably under LXC/debci, so skip it for the time being. |
Michael Biebl <biebl@debian.org> | no | 2022-12-13 | ||
| debian/localectl-disable-keymap-support.patch | localectl-disable-keymap-support We no longer support old debianisms such as /etc/default/keyboard, so disable the keymap interface in localectl until a definitive solution is found. Update the test suite to skip tests for unsupported localectl features. |
Luca Boccassi <bluca@debian.org> | no | 2023-02-08 |