Systemd 255 Issue Affects System Manager

After four months of development, the release of Systemd 255 has been announced (presented by the Systemd developers). This system manager brings several important improvements to the table.

Key changes in this new release include:

  • The addition of the component “systemd-storagetm“. This component allows for the automatic exportation of local block devices using the NVMe-TCP driver. It provides the capability to connect NVMe drives over a network using the TCP protocol. The new unit responsible for this feature is called Storage-target-mode.Target, which can be activated during the boot process by specifying the kernel parameter “RD.SystemD.unit=storage-target-mode.target”. This allows for remote access to the drive for diagnostic purposes, for example.
  • The addition of the component “systemd-bsod“. This component implements the concept of a “blue screen” or “blue screen of death” during the boot process. It displays reports of critical errors in the form of a full-screen notification.
  • The implementation of the utility “systemd-vmspawn“. This utility serves as an alternative to NSPAWN for launching an operating system image in a virtual machine. While Systemd-SSPAWN is designed for launching containers, Systemd-VMSPAWN provides a similar interface for virtual machines. Currently, only a backend based on Qemu is available for launching virtual machines.
  • The addition of the utility “varlinkctl“. This utility allows for the invocation and introduction of services using the varlink protocol.
  • The addition of the utility “systemd-pcrlock“.
/Reports, release notes, official announcements.