Releases · systemd/systemd · GitHub

CHANGES WITH 258 in spe: Incompatible changes: * Support for cgroup v1 ('legacy' and 'hybrid' hierarchies) has been removed. cgroup v2 ('unified' hierarchy) will always be mounted during system bootup and systemd-nspawn container initialization. * The minimum kernel baseline version has been bumped to v5.4 (released in 2019), with the recommended version now going up to v5.7. Consult the README file for a list of required kernel APIs. * The default access mode of tty/pts device nodes has been changed to 0600, which was 0620 in the older releases, due to general security concerns about terminals being written to by other users. To restore the old default access mode, use the '-Dtty-mode=0620' meson build option. (This effectively means "mesg n" is now the default, rather than "mesg y", see mesg(1) man page for help.) * systemd-run's --expand-environment= switch, which was disabled by default when combined with --scope, has been changed to be enabled by default. This brings cmdline expansion of transient scopes on par with services. * systemd-logind PAM sessions that previously were automatically determined to be of class "background", and which are owned by root or system accounts, will now automatically be set to class "background-light" instead. PAM sessions that previously were automatically determined to be of class "user", and which are owned by non-root system users, will now automatically be set to class "user-light" instead. This effectively means that cron jobs or FTP sessions (i.e. all PAM sessions that have no TTY assigned and neither are graphical) for system users no longer pull in a service manager by default. This behaviour can be changed by explicitly setting the session class (for example via the class= parameter to pam_systemd.so, or by setting the XDG_SESSION_CLASS environment variable as input for the service's PAM stack). This change does not affect graphical sessions, nor does it affect regular users. This is an incompatible change of sorts, sin