Systemd 232 Coming Soon With Numerous New Features
Systemd 232 is right around the corner to succeed the systemd 231 release from July.
In preparing for the upcoming systemd 232 release, the change-log has been filled out.
First up is the new systemd-mount utility as systemd's own mount alternative. Systemd 232 will also allow .automount units being transient, among other disk-related changes, including better support for NVMe devices.
Systemd 232 will also support creating users dynamically for the lifetime of a service before being automatically destroyed. This is done via DynamicUser=yes.
New options for systemd include RemoveIPC=, MemorySwapMax=, PrivateUsers=, and various new sub-commands. Some other changes include support for the cgroup namespace in systemd-nspawn, support for the CPU controller in the unified cgroup hierarchy, /efi as the mount point for the EFI boot partition if it's present and not configured via other means, FreeBSD bhyve virtualization detection, various new networking offload capabilities, and various other changes as noted from the change-log in the link above.
In preparing for the upcoming systemd 232 release, the change-log has been filled out.
First up is the new systemd-mount utility as systemd's own mount alternative. Systemd 232 will also allow .automount units being transient, among other disk-related changes, including better support for NVMe devices.
Systemd 232 will also support creating users dynamically for the lifetime of a service before being automatically destroyed. This is done via DynamicUser=yes.
New options for systemd include RemoveIPC=, MemorySwapMax=, PrivateUsers=, and various new sub-commands. Some other changes include support for the cgroup namespace in systemd-nspawn, support for the CPU controller in the unified cgroup hierarchy, /efi as the mount point for the EFI boot partition if it's present and not configured via other means, FreeBSD bhyve virtualization detection, various new networking offload capabilities, and various other changes as noted from the change-log in the link above.
36 Comments