HALF ECHO LEARN / REFERENCE COLLECTION
v262.2NEWS
Git blob: b0d42b491c5b5bbc5168dc8d19d77308851d87df
Lines 5001–6000 of 23,379
* systemd-repart's CopyBlocks= directive can now use a character device
as source (in addition to previously supported regular files and
block devices). This is useful for initializing a partition from
/dev/urandom or similar.
* systemd-repart gained new Compression= and CompressionLevel= settings
to enable internal compression in filesystems created offline.
* systemd-repart understands a new MakeSymlinks= option to create one
or more symlinks (each specified as a symlink name and target) within
a newly formatted file system.
* systemd-repart gained a new SupplementFor= setting that allows
allocating a partition only if some other existing partition cannot
be adjusted to match the constraints defined for it. This is useful
to generate an XBOOTLDR partition if and only if an ESP already
exists that is too small for the required constraints.
* The default size of verity hash partitions is now automatically
derived from SizeMaxBytes= of the data partition it is protecting.
systemd-ssh-proxy:
* systemd-ssh-proxy now also supports the AF_UNIX-based "VSOCK MUX"
protocol used by CloudHypervisor/Firecracker to expose AF_VSOCK
sockets of the VM on the host. Or in other words: it's now possible
to directly connect to ssh via AF_VSOCK from hosts to VMs of these
two hypervisors (previously this was only supported for hypervisors
which expose AF_VSOCK on the host as AF_VSOCK, such as qemu).
* systemd-ssh-proxy can now reference local VMs by their name: connect
to any local VM "foobar" registered with systemd-machined via "ssh
machine/foobar" using the AF_VSOCK protocol.
systemd-analyze:
* systemd-analyze will now show the SMBIOS #11 vendor strings set for
the machine with a new 'smbios11' verb.
* systemd-analyze gained a new --instance= option that can be used to
provide an instance name to analyze multiple templates instantiated
with the same instance name.
* systemd-analyze's "capability" verb now gained a new --mask
parameter. A numeric capability mask can be specified which is decoded
for its contained capabilities.
* systemd-analyze's "plot" verb gained two new settings: --scale-svg=
allows the X axis of the plot to be stretched by a factor. If
--detailed is specified activation timestamps are shown in the plot.
busctl:
* 'busctl monitor' gained new options --limit-messages= and --timeout=
to set the number of matches or limit the runtime of the command.
* busctl now supports doing method calls with embedded unix file
descriptors.
* busctl acquired a new "wait" command to wait for a specific signal to
arrive.
systemd-nspawn:
* systemd-nspawn --bind-user= will now propagate the bound user's SSH
public key (if included in the user record) into the container,
ensuring that any such bound user is directly accessible via ssh.
* systemd-nspawn now supports unprivileged FUSE inside containers.
systemd-importd:
* A new generator systemd-import-generator has been added to synthesize
image download jobs. This provides functionality similar to
importctl, but is configured via the kernel command line and system
credentials. It may be used to automatically download sysext,
confext, portable service, nspawn container or vmspawn VM images at
boot.
* systemd-importd now provides a Varlink IPC interface, in addition to
its existing D-Bus IPC interface.
* The individual import/export tools will now display a nice progress
bar when downloading files.
systemd-userdb & systemd-homed:
* userdbctl gained a pair of switches --uid-min= and --uid-max= to
filter the UID/GID range of the listed users or groups. It also
gained a new switch --disposition= to filter them by disposition
(i.e. show only system users or only regular users, and so on). It
also gained a new switch --fuzzy that permits a "fuzzy" search for a
user, i.e. doing a substring and string distance search, and looking
into the real name field of the user and other similar fields. It
gained a new switch --boundaries=no for disabling display of the
UID/GID range boundaries in its output.
* User records learnt a new set of fields that may list field names
that may be changed by the user themselves without requiring
administrator authentication. This new field is honoured by
systemd-homed to allow users to change selected properties of their
own user records.
systemd-run & run0:
* run0 gained a new pair of settings --pty and --pipe that control
whether to invoke the specified binary on a freshly allocated pseudo
TTY, or whether to pass the client's STDIN/STDOUT/STDERR through
directly.
* run0 gained a new switch --shell-prompt-prefix= that permits passing
in a string to display on each shell prompt as prefix. If not
specified otherwise this will show a superhero emoji (🦸), in order
to visually communicate the temporarily elevated privileges a run0
session provides. This makes use of the $SHELL_PROMPT_PREFIX
environment variables mentioned below.
* systemd-run can output some of its runtime data in JSON format via
the new --json= option.
systemd-tmpfiles:
* systemd-tmpfiles --purge switch now requires specification of at
least one tmpfiles.d/ drop-in file.
* tmpfiles.d/ files gained a new '?' specifier for the 'L' line type to
create a symlink only if the source exists, and gracefully skip the
line otherwise.
Miscellaneous:
* systemctl now supports the --now option with the 'reenable' verb.
* systemd-mount can now output JSON with a new --json= switch, for use
with --list-devices. It also shows the "diskseq" property in the
block device list.
* systemd-id128 gained a new 'var-partition-uuid' verb to calculate
the DPS UUID for /var/ keyed by the local machine-id.
* localectl gained a -l/--full option to show output without
ellipsization.
* timedatectl now supports interactive polkit authorization.
* The new Linux mseal(), listmount(), statmount() syscalls have been
added to relevant system call groups.
* The systemd-ask-password logic has been extended with a per-user
scope, i.e. user programs may now ask for passwords via the same
mechanism and the previously system-wide only mechanism.
* A new set of system/service credentials are added:
shell.prompt.prefix, shell.prompt.suffix and shell.welcome. At login
time these are propagated into the $SHELL_PROMPT_PREFIX,
$SHELL_PROMPT_SUFFIX, $SHELL_PROMPT_WELCOME environment
variables. These in turn are included in the shell prompt of
interactive shells and shown at login time, via
/etc/profile.d/70-systemd-shell-extra.sh. This functionality is
useful to visually highlight the fact a specific shell prompt
originates from a specific system, execution context or tool. These
credentials and environment variables are supposed to be generically
useful within and outside of the immediate systemd context. It is
also used by 'run0', see above.
* New RELEASE_TYPE=, EXPERIMENT=, EXPERIMENT_URL= fields have been
defined for the /etc/os-release file. For example,
"RELEASE_TYPE=development|stable|lts" can be used to indicate various
stages of the release life cycle, and "RELEASE_TYPE=experimental" can
indicate experimental builds, with the EXPERIMENT= field providing a
human-readable description of the nature of the experiment.
* A new sleep.conf HibernateOnACPower= option has been added, which
when disabled will suppress hibernation in suspend-then-hibernate
mode until the system is disconnected from a power source.
* A bunch of patches to ease building against musl have been merged.
* The various components that display progress bars
(i.e. systemd-repart, systemd-sysupdate/updatectl, importctl), will
now also issue the ANSI sequences for progress reports that Windows
Terminal understands. Most Linux terminals currently do not support
this sequence (and ignore it), but hopefully this will change one
day. The progress information is used to display a nice progress
animation in the terminal tab and icon. For details about the ANSI
sequence and its effects, see:
https://github.com/microsoft/terminal/pull/8055
https://conemu.github.io/en/AnsiEscapeCodes.html#ConEmu_specific_OSC
* systemd-sysusers is now able to create fully locked user
accounts. For compatibility it so far created accounts with a locked
(i.e. invalid) password, but not marked locked as a whole. With the
new "!" modifier for "u" lines, it is now possible to create fully
locked accounts. The distinction between accounts with a locked
password and fully locked accounts is relevant when considering
non-password forms of authentication, i.e. SSH and such. It is
strongly recommended to make use of this new feature for almost all
system accounts, since they usually do not require (and should not
permit) interactive logins. All of systemd's own system users have
been changed to be marked as fully locked.
* systemd-coredump now supports a new EnterNamespace= option, which
defaults to off. If enabled systemd-coredump will access the mount
namespace of any crashed process to acquire debug symbol information,
in order to be able to symbolize backtraces. This option is useful to
improve backtraces of processes of containerized applications. (Note
that the host systemd-coredump preferably dispatches coredump
processing to the container itself, if it supports that. Only full-OS
containers which run systemd inside will support this however, in
other cases EnterNamespace= might be a suitable approach to acquire
symbolized backtraces.)
Special thanks to Nick Owens for bringing attention to and testing
fixes for issue #34516.
Contributions from: 12paper, A. Wilcox, Abderrahim Kitouni,
Adrian Vovk, Alain Greppin, Allison Karlitskaya, Alyssa Ross,
Anders Jonsson, Andika Triwidada, Andreas Schwab, Andres Beltran,
Ani Sinha, Anouk Ceyssens, Anselm Schueler, Anton Golubev,
Antonio Alvarez Feijoo, Arian van Putten, Arnaud Patard,
Arthur Shau, Bastien Nocera, Benjamin ROBIN, Brenton Simpson,
Bryan Gurney, ButterflyOfFire, Carlo Teubner, Celeste Liu,
Chen Guanqiao, Chen Qi, Chengen Du, Christian Hesse,
Christoph Anton Mitterer, Colin Foster, Collin L,
Cristian Rodríguez, Daan De Meyer, Dan Nicholson, Daniel Dawson,
Daniel Martinez, Daniel P. Berrangé, Daniel Rusek,
Darsey Litzenberger, David Joaquín Shourabi Porcel,
David Michael, David Rheinsberg, David Tardon, Davide Cavalca,
Derek J. Clark, Diego Viola, Dimitrys Meliates, Diogo Ivo,
Dmytro Markevych, DocNITE, Dominique Martinet,
Dr. David Alan Gilbert, Edson Juliano Drosdeck, Erik Sjölund,
Etienne Champetier, Etienne Cordonnier, Ettore Atalan,
Eugeny Shcheglov, Excited-bore, Fabian Vogt, Federico Giovanardi,
Filip Lewiński, Florian Schmaus, Franck Bui, Frantisek Sumsal,
Fábio Rodrigues Ribeiro, Gabriel Elyas, Gaël PORTAY,
Geraldo S. Simião Kutz, Giovanni Baratta, Greg Heartsfield,
Gregor Herburger, Gregory Arenius, GwynBleidD, Göran Uddeborg,
Hans de Goede, Helmut Grohne, Henry Chen, Ian Abbott, Integral,
Ivan Kruglov, Ivan Shapovalov, James Coglan, James Hilliard,
James Muir, Jason Yundt, Jeffrey Bosboom, Jian Zhang,
Jiri Grönroos, Johannes Schneider, John A. Leuenhagen,
Jose Ignacio Tornos Martinez, JoseskVolpe, Joshua Grisham,
Jörg Behrmann, Kai-Chuan Hsieh, Kamil Szczęk, Karel Zak,
Kornilios Kourtis, Kuntal Majumder, Lennart Poettering,
Lidong Zhong, Luca Boccassi, Lucas Adriano Salles,
Lucas Werkmeister, Ludwig Nussel, Luke T. Shumaker,
Lukáš Nykrýn, Luna Jernberg, Léane GRASSER, Maanya Goenka,
Mantas Mikulėnas, Marc Reisner, Marcel Hellwig, Marco Tomaschett,
Marin Kresic, Marius Hoch, Martin Srebotnjak, Martin Wilck,
Mary Strodl, Matteo Croce, Matthias Lisin, Matthias Schiffer,
Matthieu Baerts (NGI0), Matthieu CHARETTE,
Mauri de Souza Meneguzzo, Maximilian Wilhelm, Merlin Jehli,
Michael Ferrari, Michal Koutný, Michal Sekletár, Michał Górny,
Michele Dionisio, Michiel, Mickaël Salaün, Mike Gilbert,
Mike Yuan, MkKvcs, Nick Cao, Nick Rosbrook, Nils K, Nova840,
Oğuz Ersen, Pavel Borecki, PavlNekrasov, Peter Hutterer,
Peter Rajnoha, Piotr Drąg, Raphaël Mélotte, Renan Guilherme,
Renjaya Raga Zenta, Ricky Tigg, Riku, Robin Lee, Ronan Pigott,
Ryan Wilson, Sam James, Sascha Mester, Sean Rhodes,
Sebastian Gross, Septatrix, Sergey A, ShreyasMahangade,
Simon Pilkington, Skye Chappelle, Steve Traylen, Stuart Hayhurst,
SuhailAhmedVelorum, Susant Sahani, Takeo Kondo, Temuri Doghonadze,
Thomas Blume, Thorsten Kukuk, Thorsten Scherer, Tobias Fleig,
Tobias Zimmermann, Tom Coldrick, Tom Yan, Tomas Bzatek,
Topi Miettinen, Tristan F.-R., Uday Shankar, Valentin David,
Vasiliy Kovalev, Vitaly Kuznetsov, Vito Caputo, Vladimir Panteleev,
Vursc, Will Fancher, WilliButz, Winterhuman, Xeonacid, Xuanjun Wen,
Yanqing Jing, Yaron Shahrabani, Yu Watanabe, Yuri Chornoivan,
ZHANG Yuntian, Zbigniew Jędrzejewski-Szmek, Zhou Qiankang,
andre4ik3, anonymix007, bryango, chayleaf, chenjiayi, csp5me, cvlc12,
fwfy, gerblesh, hugo303, jan@neighbourhood.ie, jauge-technica,
lumingzh, maia x., marginaldev, migleeson, nerdopolis, oldherl,
pyfisch, q66, rajmohan r, reDBo0n, rhellstrom, rindeal, samuelvw01,
sinus-x, tfg13, vdovhanych, xujing, Łukasz Stelmach,
Štěpán Němec, Дамјан Георгиевски, 白一百
— Edinburgh, 2024-12-10
CHANGES WITH 256:
Announcements of Future Feature Removals and Incompatible Changes:
* Support for automatic flushing of the nscd user/group database caches
will be dropped in a future release.
* Support for cgroup v1 ('legacy' and 'hybrid' hierarchies) is now
considered obsolete and systemd by default will refuse to boot under
it. To forcibly reenable cgroup v1 support,
SYSTEMD_CGROUP_ENABLE_LEGACY_FORCE=1 must be set on kernel command
line. The meson option '-Ddefault-hierarchy=' is also deprecated, and
only cgroup v2 ('unified' hierarchy) can be selected as the build-time
default.
* Support for System V service scripts is deprecated and will be
removed in a future release. Please make sure to update your software
*now* to include a native systemd unit file instead of a legacy
System V script to retain compatibility with future systemd releases.
* Support for the SystemdOptions EFI variable is deprecated.
'bootctl systemd-efi-options' will emit a warning when used. It seems
that this feature is little-used and it is better to use alternative
approaches like credentials and confexts. The plan is to drop support
altogether at a later point, but this might be revisited based on
user feedback.
* systemd-run's switch --expand-environment= which currently is disabled
by default when combined with --scope, will be changed in a future
release to be enabled by default.
* Previously, systemd-networkd did not explicitly remove any bridge
VLAN IDs assigned on bridge master and ports. Since version 256, if a
.network file for an interface has at least one valid setting in the
[BridgeVLAN] section, then all assigned VLAN IDs on the interface
that are not configured in the .network file are removed.
* IPForward= setting in .network file is deprecated and replaced with
IPv4Forwarding= and IPv6Forwarding= settings. These new settings are
supported both in .network file and networkd.conf. If specified in a
.network file, they control corresponding per-link settings. If
specified in networkd.conf, they control corresponding global
settings. Note, previously IPv6SendRA= and IPMasquerade= implied
IPForward=, but now they imply the new per-link settings. One of the
simplest ways to migrate configurations, that worked as a router with
the previous version, is enabling both IPv4Forwarding= and
IPv6Forwarding= in networkd.conf. See systemd.network(5) and
networkd.conf(5) for more details.
* systemd-gpt-auto-generator will stop generating units for ESP or
XBOOTLDR partitions if it finds mount entries for or below the /boot/
or /efi/ hierarchies in /etc/fstab. This is to prevent the generator
from interfering with systems where the ESP is explicitly configured
to be mounted at some path, for example /boot/efi/ (this type of
setup is obsolete, but still commonly found).
* The behavior of systemd-sleep and systemd-homed has been updated to
freeze user sessions when entering the various sleep modes or when
locking a homed-managed home area. This is known to cause issues with
the proprietary NVIDIA drivers. Packagers of the NVIDIA proprietary
drivers may want to add drop-in configuration files that set
SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false for systemd-suspend.service
and related services, and SYSTEMD_HOME_LOCK_FREEZE_SESSION=false for
systemd-homed.service.
* systemd-tmpfiles and systemd-sysusers, when given a relative
configuration file path (with at least one directory separator '/'),
will open the file directly, instead of searching for the given
partial path in the standard locations. The old mode wasn't useful
because tmpfiles.d/ and sysusers.d/ configuration has a flat
structure with no subdirectories under the standard locations and
this change makes it easier to work with local files with those
tools.
* systemd-tmpfiles now properly applies nested configuration to 'R' and
'D' stanzas. For example, with the combination of 'R /foo' and 'x
/foo/bar', /foo/bar will now be excluded from removal.
* systemd.crash_reboot and related settings are deprecated in favor of
systemd.crash_action=.
* Stable releases for version v256 and newer will now be pushed in the
main repository. The systemd-stable repository will be used for existing
stable branches (v255-stable and lower), and when they reach EOL it will
be archived.
General Changes and New Features:
* Various programs will now attempt to load the main configuration file
from locations below /usr/lib/, /usr/local/lib/, and /run/, not just
below /etc/. For example, systemd-logind will look for
/etc/systemd/logind.conf, /run/systemd/logind.conf,
/usr/local/lib/systemd/logind.conf, and /usr/lib/systemd/logind.conf,
and use the first file that is found. This means that the search
logic for the main config file and for drop-ins is now the same.
Similarly, kernel-install will look for the config files in
/usr/lib/kernel/ and the other search locations, and now also
supports drop-ins.
systemd-udevd now supports drop-ins for udev.conf.
* A new 'systemd-vpick' binary has been added. It implements the new
vpick protocol, where a "*.v/" directory may contain multiple files
which have versions (following the UAPI version format specification)
embedded in the file name. The files are ordered by version and
the newest one is selected.
systemd-nspawn --image=/--directory=, systemd-dissect,
systemd-portabled, and the RootDirectory=, RootImage=,
ExtensionImages=, and ExtensionDirectories= settings for units now
support the vpick protocol and allow the latest version to be
selected automatically if a "*.v/" directory is specified as the
source.
* Encrypted service credentials can now be made accessible to
unprivileged users. systemd-creds gained new options --user/--uid=
for encrypting/decrypting a credential for a specific user.
* New command-line tool 'importctl' to download, import, and export
disk images via systemd-importd is added with the following verbs:
pull-tar, pull-raw, import-tar, import-raw, import-fs, export-tar,
export-raw, list-transfers, and cancel-transfer. This functionality
was previously available in "machinectl", where it was used
exclusively for machine images. The new "importctl" generalizes this
for sysext, confext, and portable service images.
* The systemd sources may now be compiled cleanly with all OpenSSL 3.0
deprecations removed, including the OpenSSL engine logic turned off.
Service Management:
* New system manager setting ProtectSystem= has been added. It is
analogous to the unit setting, but applies to the whole system. It is
enabled by default in the initrd.
Note that this means that code executed in the initrd cannot naively
expect to be able to write to /usr/ during boot. This affects
dracut <= 101, which wrote "hooks" to /lib/dracut/hooks/. See
https://github.com/dracut-ng/dracut-ng/commit/a45048b80c27ee5a45a380.
* New unit setting WantsMountsFor= has been added. It is analogous to
RequiresMountsFor=, but creates a Wants= dependency instead of
Requires=. This new logic is now used in various places where mounts
were added as dependencies for other settings (WorkingDirectory=-…,
PrivateTmp=yes, cryptsetup lines with 'nofail').
* New unit setting MemoryZSwapWriteback= can be used to control the new
memory.zswap.writeback cgroup knob added in kernel 6.8.
* The manager gained a org.freedesktop.systemd1.StartAuxiliaryScope()
D-Bus method to devolve some processes from a service into a new
scope. This new scope will remain running, even when the original
service unit is restarted or stopped. This allows a service unit to
split out some worker processes which need to continue running.
Control group properties of the new scope are copied from the
originating unit, so various limits are retained.
* Units now expose properties EffectiveMemoryMax=,
EffectiveMemoryHigh=, and EffectiveTasksMax=, which report the
most stringent limit systemd is aware of for the given unit.
* A new unit file specifier %D expands to $XDG_DATA_HOME (for user
services) or /usr/share/ (for system services).
* AllowedCPUs= now supports specifier expansion.
* What= setting in .mount and .swap units now accepts fstab-style
identifiers, for example UUID=… or LABEL=….
* RestrictNetworkInterfaces= now supports alternative network interface
names.
* PAMName= now implies SetLoginEnvironment=yes.
* systemd.firstboot=no can be used on the kernel command-line to
disable interactive queries, but allow other first boot configuration
to happen based on credentials.
* The system's hostname can be configured via the systemd.hostname
system credential.
* The systemd binary will no longer chainload sysvinit's "telinit"
binary when called under the init/telinit name on a system that isn't
booted with systemd. This previously has been supported to make sure
a distribution that has both init systems installed can reasonably
switch from one to the other via a simple reboot. Distributions
apparently have lost interest in this, and the functionality has not
been supported on the primary distribution this was still intended
for a long time, and hence has been removed now.
* A new concept called "capsules" has been introduced. "Capsules" wrap
additional per-user service managers, whose users are transient and
are only defined as long as the service manager is running. (This is
implemented via DynamicUser=1), allowing a user manager to be used to
manage a group of processes without needing to create an actual user
account. These service managers run with home directories of
/var/lib/capsules/<capsule-name> and can contain regular services and
other units. A capsule is started via a simple "systemctl start
capsule@<name>.service". See the capsule@.service(5) man page for
further details.
Various systemd tools (including, and most importantly, systemctl and
systemd-run) have been updated to interact with capsules via the new
"--capsule="/"-C" switch.
* .socket units gained a new setting PassFileDescriptorsToExec=, taking
a boolean value. If set to true the file descriptors the socket unit
encapsulates are passed to the ExecStartPost=, ExecStopPre=,
ExecStopPost= using the usual $LISTEN_FDS interface. This may be used
for doing additional initializations on the sockets once they are
allocated. (For example, to install an additional eBPF program on
them).
* The .socket setting MaxConnectionsPerSource= (which so far put a
limit on concurrent connections per IP in Accept=yes socket units),
now also has an effect on AF_UNIX sockets: it will put a limit on the
number of simultaneous connections from the same source UID (as
determined via SO_PEERCRED). This is useful for implementing IPC
services in a simple Accept=yes mode.
* The service manager will now maintain a counter of soft reboot cycles
the system went through. It may be queried via the D-Bus APIs.
* systemd's execution logic now supports the new pidfd_spawn() API
introduced by glibc 2.39, which allows us to invoke a subprocess in a
target cgroup and get a pidfd back in a single operation.
* systemd/PID 1 will now send an additional sd_notify() message to its
supervising VMM or container manager reporting the selected hostname
("X_SYSTEMD_HOSTNAME=") and machine ID ("X_SYSTEMD_MACHINE_ID=") at
boot. Moreover, the service manager will send additional sd_notify()
messages ("X_SYSTEMD_UNIT_ACTIVE=") whenever a target unit is
reached. This can be used by VMMs/container managers to schedule
access to the system precisely. For example, the moment a system
reports "ssh-access.target" being reached a VMM/container manager
knows it can now connect to the system via SSH. Finally, a new
sd_notify() message ("X_SYSTEMD_SIGNALS_LEVEL=2") is sent the moment
PID 1 has successfully completed installation of its various UNIX
process signal handlers (i.e. the moment where SIGRTMIN+4 sent to
PID 1 will start to have the effect of shutting down the system
cleanly). X_SYSTEMD_SHUTDOWN= is sent shortly before the system shuts
down, and carries a string identifying the type of shutdown,
i.e. "poweroff", "halt", "reboot". X_SYSTEMD_REBOOT_PARAMETER= is
sent at the same time and carries the string passed to "systemctl
--reboot-argument=" if there was one.
* New D-Bus properties ExecMainHandoffTimestamp and
ExecMainHandoffTimestampMonotonic are now published by services
units. This timestamp is taken as the very last operation before
handing off control to invoked binaries. This information is
available for other unit types that fork off processes (i.e. mount,
swap, socket units), but currently only via "systemd-analyze dump".
* An additional timestamp is now taken by the service manager when a
system shutdown operation is initiated. It can be queried via D-Bus
during the shutdown phase. It's passed to the following service
manager invocation on soft reboots, which will then use it to log the
overall "grey-out" time of the soft reboot operation, i.e. the time
when the shutdown began until the system is fully up again.
* "systemctl status" will now display the invocation ID in its usual
output, i.e. the 128bit ID uniquely assigned to the current runtime
cycle of the unit. The ID has been supported for a long time, but is
now more prominently displayed, as it is a very useful handle to a
specific invocation of a service.
* systemd now generates a new "taint" string "unmerged-bin" for systems
that have /usr/bin/ and /usr/sbin/ separate. It's generally
recommended to make the latter a symlink to the former these days.
* A new systemd.crash_action= kernel command line option has been added
that configures what to do after the system manager (PID 1) crashes.
This can also be configured through CrashAction= in systemd.conf.
* "systemctl kill" now supports --wait which will make the command wait
until the signalled services terminate.
Journal:
* systemd-journald can now forward journal entries to a socket
(AF_INET, AF_INET6, AF_UNIX, or AF_VSOCK). The socket can be
specified in journald.conf via a new option ForwardToSocket= or via
the 'journald.forward_to_socket' credential. Log records are sent in
the Journal Export Format. A related setting MaxLevelSocket= has been
added to control the maximum log levels for the messages sent to this
socket.
* systemd-journald now also reads the journal.storage credential when
determining where to store journal files.
* systemd-vmspawn gained a new --forward-journal= option to forward the
virtual machine's journal entries to the host. This is done over a
AF_VSOCK socket, i.e. it does not require networking in the guest.
* journalctl gained option '-i' as a shortcut for --file=.
* journalctl gained a new -T/--exclude-identifier= option to filter
out certain syslog identifiers.
* journalctl gained a new --list-namespaces option.
* systemd-journal-remote now also accepts AF_VSOCK and AF_UNIX sockets
(so it can be used to receive entries forwarded by systemd-journald).
* systemd-journal-gatewayd allows restricting the time range of
retrieved entries with a new "realtime=[<since>]:[<until>]" URL
parameter.
* systemd-cat gained a new option --namespace= to specify the target
journal namespace to which the output shall be connected.
* systemd-bsod gained a new option --tty= to specify the output TTY
Device Management:
* /dev/ now contains symlinks that combine by-path and by-{label,uuid}
information:
/dev/disk/by-path/<path>/by-<label|uuid|…>/<label|uuid|…>
This allows distinguishing partitions with identical contents on
multiple storage devices. This is useful, for example, when copying
raw disk contents between devices.
* systemd-udevd now creates persistent /dev/media/by-path/ symlinks for
media controllers. For example, the uvcvideo driver may create
/dev/media0 which will be linked as
/dev/media/by-path/pci-0000:04:00.3-usb-0:1:1.0-media-controller.
* A new unit systemd-udev-load-credentials.service has been added
to pick up udev.conf drop-ins and udev rules from credentials.
* 'udevadm test' and 'udevadm test-builtin' commands now do not change
any settings; sysfs attributes, sysctls, udev database and so on.
E.g. 'udevadm test-builtin net_setup_link /sys/class/net/INTERFACE'
does not change any interface settings, but only prints which .link
file matches the interface. So, even privileged users can safely
invoke the commands.
* An allowlist/denylist may be specified to filter which sysfs
attributes are used when crafting network interface names. Those
lists are stored as hwdb entries
ID_NET_NAME_ALLOW_<sysfsattr>=0|1
and
ID_NET_NAME_ALLOW=0|1.
The goal is to avoid unexpected changes to interface names when the
kernel is updated and new sysfs attributes become visible.
* A new unit tpm2.target has been added to provide a synchronization
point for units which expect the TPM hardware to be available. A new
generator "systemd-tpm2-generator" has been added that will insert
this target whenever it detects that the firmware has initialized a
TPM, but Linux hasn't loaded a driver for it yet.
* systemd-backlight now properly supports numbered devices which the
kernel creates to avoid collisions in the leds subsystem.
* systemd-hwdb update operation can be disabled with a new environment
variable SYSTEMD_HWDB_UPDATE_BYPASS=1.
systemd-hostnamed:
* systemd-hostnamed now exposes the machine ID and boot ID via
D-Bus. It also exposes the hosts AF_VSOCK CID, if available.
* systemd-hostnamed now provides a basic Varlink interface.
* systemd-hostnamed exports the full data in os-release(5) and
machine-info(5) via D-Bus and Varlink.
* hostnamectl now shows the system's product UUID and hardware serial
number if known.
Network Management:
* systemd-networkd now provides a basic Varlink interface.
* systemd-networkd's ARP proxy support gained a new option to configure
a private VLAN variant of the proxy ARP supported by the kernel under
the name IPv4ProxyARPPrivateVLAN=.
* systemd-networkd now exports the NamespaceId and NamespaceNSID
properties via D-Bus and Varlink. (which expose the inode and NSID of
the network namespace the networkd instance manages)
* systemd-networkd now supports IPv6RetransmissionTimeSec= and
UseRetransmissionTime= settings in .network files to configure
retransmission time for IPv6 neighbor solicitation messages.
* networkctl gained new verbs 'mask' and 'unmask' for masking networkd
configuration files such as .network files.
* 'networkctl edit --runtime' allows editing volatile configuration
under /run/systemd/network/.
* The implementation behind TTLPropagate= network setting has been
removed and the setting is now ignored.
* systemd-network-generator will now pick up .netdev/.link/.network/
networkd.conf configuration from system credentials.
* systemd-networkd will now pick up wireguard secrets from
credentials.
* systemd-networkd's Varlink API now supports enumerating LLDP peers.
* .link files now support new Property=, ImportProperty=,
UnsetProperty= fields for setting udev properties on a link.
* The various .link files that systemd ships for interfaces that are
supposed to be managed by systemd-networkd only now carry a
ID_NET_MANAGED_BY=io.systemd.Network udev property ensuring that
other network management solutions honouring this udev property do
not come into conflict with networkd, trying to manage these
interfaces.
* .link files now support a new ReceivePacketSteeringCPUMask= setting
for configuring which CPUs to steer incoming packets to.
* The [Network] section in .network files gained a new setting
UseDomains=, which is a single generic knob for controlling the
settings of the same name in the [DHCPv4], [DHCPv6] and
[IPv6AcceptRA].
* The 99-default.link file we ship by default (that defines the policy
for all network devices to which no other .link file applies) now
lists "mac" among AlternativeNamesPolicy=. This means that network
interfaces will now by default gain an additional MAC-address based
alternative device name. (i.e. enx…)
systemd-nspawn:
* systemd-nspawn now provides a /run/systemd/nspawn/unix-export/
directory where the container payload can expose AF_UNIX sockets to
allow them to be accessed from outside.
* systemd-nspawn will tint the terminal background for containers in a
blueish color. This can be controller with the new --background=
switch or the new $SYSTEMD_TINT_BACKGROUND environment variable.
* systemd-nspawn gained support for the 'owneridmap' option for --bind=
mounts to map the target directory owner from inside the container to
the owner of the directory bound from the host filesystem.
* systemd-nspawn now supports moving Wi-Fi network devices into a
container, just like other network interfaces.
systemd-resolved:
* systemd-resolved now reads RFC 8914 EDE error codes provided by
upstream DNS services.
* systemd-resolved and resolvectl now support RFC 9460 SVCB and HTTPS
records, as well as RFC 2915 NAPTR records.
* resolvectl gained a new option --relax-single-label= to allow
querying single-label hostnames via unicast DNS on a per-query basis.
* systemd-resolved's Varlink IPC interface now supports resolving
DNS-SD services as well as an API for resolving raw DNS RRs.
* systemd-resolved's .dnssd DNS_SD service description files now
support DNS-SD "subtypes" via the new SubType= setting.
* systemd-resolved's configuration may now be reloaded without
restarting the service. (i.e. "systemctl reload systemd-resolved" is
now supported)
SSH Integration:
* An sshd_config drop-in to allow ssh keys acquired via userdbctl (for
example expose by homed accounts) to be used for authorization of
incoming SSH connections. This uses the AuthorizedKeysCommand stanza
of sshd_config. Note that sshd only allows a single command to be
configured this way, hence this drop-in might conflict with other
uses of the logic. It is possible to chainload another, similar tool
of another subsystem via the --chain switch of userdbctl, to support
both in parallel. See the "INTEGRATION WITH SSH" section in
userdbctl(1) for details on this. Our recommendation how to combine
other subsystem's use of the SSH authorized keys logic with systemd's
userbctl functionality however is to implement the APIs described
here: https://systemd.io/USER_GROUP_API – in that case this newly
added sshd_config integration would just work and do the right thing
for all backends.
* A small new unit generator "systemd-ssh-generator" has been added. It
checks if the sshd binary is installed. If so, it binds it via
per-connection socket activation to various sockets depending on the
execution context:
• If the system is run in a VM providing AF_VSOCK support, it
automatically binds sshd to AF_VSOCK port 22.
• If the system is invoked as a full-OS container and the container
manager pre-mounts a directory /run/host/unix-export/, it will
bind sshd to an AF_UNIX socket /run/host/unix-export/ssh. The
idea is the container manager bind mounts the directory to an
appropriate place on the host as well, so that the AF_UNIX socket
may be used to easily connect from the host to the container.
• sshd is also bound to an AF_UNIX socket
/run/ssh-unix-local/socket, which may be to use ssh/sftp in a
"sudo"-like fashion to access resources of other local users.
• Via the kernel command line option "systemd.ssh_listen=" and the
system credential "ssh.listen" sshd may be bound to additional,
explicitly configured options, including AF_INET/AF_INET6 ports.
In particular the first two mechanisms should make dealing with local
VMs and full OS containers a lot easier, as SSH connections will
*just* *work* from the host – even if no networking is available
whatsoever.
systemd-ssh-generator optionally generates a per-connection
socket activation service file wrapping sshd. This is only done if
the distribution does not provide one on its own under the name
"sshd@.service". The generated unit only works correctly if the SSH
privilege separation ("privsep") directory exists. Unfortunately
distributions vary wildly where they place this directory. An
incomprehensive list:
• /usr/share/empty.sshd/ (new fedora)
• /var/empty/
• /var/empty/sshd/
• /run/sshd/ (debian/ubuntu?)
If the SSH privsep directory is placed below /var/ or /run/ care
needs to be taken that the directory is created automatically at boot
if needed, since these directories possibly or always come up
empty. This can be done via a tmpfiles.d/ drop-in. You may use the
"sshdprivsepdir" meson option provided by systemd to configure the
directory, in case you want systemd to create the directory as needed
automatically, if your distribution does not cover this natively.
Recommendations to distributions, in order to make things just work:
• Please provide a per-connection SSH service file under the name
"sshd@.service".
• Please move the SSH privsep dir into /usr/ (so that it is truly
immutable on image-based operating systems, is strictly under
package manager control, and never requires recreation if the
system boots up with an empty /run/ or /var/).
• As an extension of this: please consider following Fedora's lead
here, and use /usr/share/empty.sshd/ to minimize needless
differences between distributions.
• If your distribution insists on placing the directory in /var/ or
/run/ then please at least provide a tmpfiles.d/ drop-in to
recreate it automatically at boot, so that the sshd binary just
works, regardless in which context it is called.
* A small tool "systemd-ssh-proxy" has been added, which is supposed to
act as counterpart to "systemd-ssh-generator". It's a small plug-in
for the SSH client (via ProxyCommand/ProxyUseFdpass) to allow it to
connect to AF_VSOCK or AF_UNIX sockets. Example: "ssh vsock/4711"
connects to a local VM with cid 4711, or "ssh
unix/run/ssh-unix-local/socket" to connect to the local host via the
AF_UNIX socket /run/ssh-unix-local/socket.
systemd-boot and systemd-stub and Related Tools:
* TPM 1.2 PCR measurement support has been removed from systemd-stub.
TPM 1.2 is obsolete and – due to the (by today's standards) weak
cryptographic algorithms it only supports – does not actually provide
the security benefits it's supposed to provide. Given that the rest
of systemd's codebase never supported TPM 1.2, the support has now
been removed from systemd-stub as well.
* systemd-stub will now measure its payload via the new EFI
Confidential Computing APIs (CC), in addition to the pre-existing
measurements to TPM.
* confexts are loaded by systemd-stub from the ESP as well.
* kernel-install gained support for --root= for the 'list' verb.
* bootctl now provides a basic Varlink interface and can be run as a
daemon via a template unit.
* systemd-measure gained new options --certificate=, --private-key=,
and --private-key-source= to allow using OpenSSL's "engines" or
"providers" as the signing mechanism to use when creating signed
TPM2 PCR measurement values.
* ukify gained support for signing of PCR signatures via OpenSSL's
engines and providers.
* ukify now supports zboot kernels.
* systemd-boot now supports passing additional kernel command line
switches to invoked kernels via an SMBIOS Type #11 string
"io.systemd.boot.kernel-cmdline-extra". This is similar to the
pre-existing support for this in systemd-stub, but also applies to
Type #1 Boot Loader Specification Entries.
* systemd-boot's automatic SecureBoot enrollment support gained support
for enrolling "dbx" too (Previously, only db/KEK/PK enrollment was
supported). It also now supports UEFI "Custom" and "Audit" modes.
* The pcrlock policy is saved in an unencrypted credential file
"pcrlock.<entry-token>.cred" under XBOOTLDR/ESP in the
/loader/credentials/ directory. It will be picked up at boot by
systemd-stub and passed to the initrd, where it can be used to unlock
the root file system.
* systemd-pcrlock gained an --entry-token= option to configure the
entry-token.
* systemd-pcrlock now provides a basic Varlink interface and can be run
as a daemon via a template unit.
* systemd-pcrlock's TPM nvindex access policy has been modified, this
means that previous pcrlock policies stored in nvindexes are
invalidated. They must be removed (systemd-pcrlock remove-policy) and
recreated (systemd-pcrlock make-policy). For the time being
systemd-pcrlock remains an experimental feature, but it is expected
to become stable in the next release, i.e. v257.
* systemd-pcrlock's --recovery-pin= switch now takes three values:
"hide", "show", "query". If "show" is selected the automatically
generated recovery PIN is shown to the user. If "query" is selected
then the PIN is queried from the user.
* sd-stub gained support for the new ".ucode" PE section in UKIs, that
may contain CPU microcode data. When control is handed over to the
Linux kernel this data is prepended to the set of initrds passed.
systemd-run/run0:
* systemd-run is now a multi-call binary. When invoked as 'run0', it
provides as interface similar to 'sudo', with all arguments starting
at the first non-option parameter being treated the command to invoke
as root. Unlike 'sudo' and similar tools, it does not make use of
setuid binaries or other privilege escalation methods, but instead
runs the specified command as a transient unit, which is started by
the system service manager, so privileges are dropped, rather than
gained, thus implementing a much more robust and safe security
model. As usual, authorization is managed via Polkit.
* systemd-run/run0 will now tint the terminal background on supported
terminals: in a reddish tone when invoking a root service, in a
yellowish tone otherwise. This may be controlled and turned off via
the new --background= switch or the new $SYSTEMD_TINT_BACKGROUND
environment variable.
* systemd-run gained a new option '--ignore-failure' to suppress
command failures.
Command-line tools:
* 'systemctl edit --stdin' allows creation of unit files and drop-ins
with contents supplied via standard input. This is useful when creating
configuration programmatically; the tool takes care of figuring out
the file name, creating any directories, and reloading the manager
afterwards.
* 'systemctl disable --now' and 'systemctl mask --now' now work
correctly with template units.
* 'systemd-analyze architectures' lists known CPU architectures.
* 'systemd-analyze --json=…' is supported for 'architectures',
'capability', 'exit-status'.
* 'systemd-tmpfiles --purge' will purge (remove) all files and
directories created via tmpfiles.d configuration.
* systemd-id128 gained new options --no-pager, --no-legend, and
-j/--json=.
* hostnamectl gained '-j' as shortcut for '--json=pretty' or
'--json=short'.
* loginctl now supports -j/--json=.
* resolvectl now supports -j/--json= for --type=.
* systemd-tmpfiles gained a new option --dry-run to print what would be
done without actually taking action.
* varlinkctl gained a new --collect switch to collect all responses of
a method call that supports multiple replies and turns it into a
single JSON array.
* systemd-dissect gained a new --make-archive option to generate an
archive file (tar.gz and similar) from a disk image.
systemd-vmspawn:
* systemd-vmspawn gained a new --firmware= option to configure or list
firmware definitions for Qemu, a new --tpm= option to enable or
disable the use of a software TPM, a new --linux= option to specify a
kernel binary for direct kernel boot, a new --initrd= option to
specify an initrd for direct kernel boot, a new -D/--directory option
to use a plain directory as the root file system, a new
--private-users option similar to the one in systemd-nspawn, new
options --bind= and --bind-ro= to bind part of the host's file system
hierarchy into the guest, a new --extra-drive= option to attach
additional storage, and -n/--network-tap/--network-user-mode to
configure networking.
* A new systemd-vmspawn@.service can be used to launch systemd-vmspawn
as a service.
* systemd-vmspawn gained the new --console= and --background= switches
that control how to interact with the VM. As before, by default an
interactive terminal interface is provided, but now with a background
tinted with a greenish hue.
* systemd-vmspawn can now register its VMs with systemd-machined,
controlled via the --register= switch.
* machinectl's start command (and related) can now invoke images either
as containers via systemd-nspawn (specified as '--runner=nspawn', the
default) or as VMs via systemd-vmspawn (specified as
'--runner=vmspawn' or '-V').