diff options
Diffstat (limited to 'debian/NEWS')
| -rw-r--r-- | debian/NEWS | 67 |
1 files changed, 67 insertions, 0 deletions
diff --git a/debian/NEWS b/debian/NEWS index ebd5237..930fe71 100644 --- a/debian/NEWS +++ b/debian/NEWS @@ -1,3 +1,70 @@ +systemd (256~rc3-3) unstable; urgency=medium + + - /tmp/ is now by default a tmpfs, via the tmp.mount unit provided upstream. + The old default setup can be retained simply by masking the unit locally + with (do not do this if you are defining /tmp/ manually in /etc/fstab): + + systemctl mask tmp.mount + + or: + + touch /etc/systemd/system/tmp.mount + + It is recommended to check /tmp/ for any leftover files before rebooting + after installing this update and manually cleaning up, as the directory + will longer be cleaned up automatically on boot, as it is overmounted. It + is always possible to remount the root filesystem in a local directory + and remove leftovers manually after rebooting, but this will not be done + automatically to avoid unintential removals. This situation can be easily + detected by checking the journal after a reboot, as there will be a log + message that says: + + tmp.mount: Directory /tmp to mount over is not empty, mounting anyway + + - /run/lock/ is no longer created with a patch before units start, but by + a standard early-boot run-lock.mount unit that is ordered before + local-fs.target. Any service needing to use /run/lock/ and running before + sysinit.target (ie, they likely define DefaultDependencies=no) will need + to be explicitly ordered with After=run-lock.mount. The two known cases + where this happens in the archive have a bug+MR filed already. + + - On new installations, tmpfiles.d will now cleanup by default files + that have not been changed or accessed on /tmp/ for 10 days, and /var/tmp/ + for 30 days. The legacy behaviour can be configured with a local override + if needed: + + echo 'D /tmp 1777' > /etc/tmpfiles.d/tmp.conf + + This override will be automatically provided for upgrades of existing + systems from previous releases to Trixie. As a reminder, individual + files and directories can be marked for exclusion from cleanups with + the 'x' type configuration line as described in the tmpfiles.d manpage, + for example: + + echo 'x /tmp/my-precious' > /etc/tmpfiles.d/precious.conf + + - coredumps are now disabled by default via configuration files rather than + an out-of-tree patch (installing the optional systemd-coredump package + will enable them as before). As always, overriding via local drop-ins is + possible if desired. The configuration files that respectively affect + the system systemd instance, the user systemd instances and PAM sessions + are: + + /usr/lib/systemd/system.conf.d/10-coredump-debian.conf + /usr/lib/systemd/user.conf.d/10-coredump-debian.conf + /usr/lib/sysctl.d/10-coredump-debian.conf + /etc/security/limits.d/10-coredump-debian.conf + + -- Luca Boccassi <bluca@debian.org> Tue, 28 May 2024 00:07:57 +0100 + +systemd (256~rc2-1) unstable; urgency=medium + + In the rare case a scheduled shutdown fails to be enqueued (most + likely, D-Bus daemon/broker is not installed), the system will now + immediately reboot, restoring the default behaviour intended upstream. + + -- Luca Boccassi <bluca@debian.org> Wed, 15 May 2024 00:40:56 +0100 + systemd (253~rc2-1) experimental; urgency=medium TuxOnIce is no longer supported directly (via an out-of-tree patch) |