On Fri, 8 Dec 2023 11:04:25 +1300, Peter Reutemann quoted:
'Today, version 255 of the Linux systemd project honors that original intent ...'
My Debian Unstable system got systemd 255 (OK, an RC version) on its last upgrade back on November 21: root(a)theon:~ # ls -l /var/cache/apt/archives/*systemd*255* ... -rw-r--r-- 1 root root 3535680 Nov 21 12:42 /var/cache/apt/archives/systemd_255~rc2-3_amd64.deb ... And yes, that includes the new systemd-bsod.service. Phoronix has a good list of the important changes <https://www.phoronix.com/news/systemd-255>. I was intrigued by this one: There's been an overhaul to the way systemd services are spawned. Rather than forking the process that shared all of the manager's memory via CoW before exec'ing the target executable, the new process is now spawned using CLONE_VM and CLONE_VFORK via posix_spawn(). posix_spawn(3) <https://manpages.debian.org/3/posix_spawn.3.html> was defined by POSIX to allow implementation on machines which could not handle a full fork(2) call. However, on Linux, it is implemented via the abovementioned options to the clone(2) <manpages.debian.org/2/clone.2.html> call, just as a more efficient alternative to the traditional *nix fork-followed-by-exec sequence. Also, there is this new use of varlink, which I hadn’t heard of before <https://varlink.org/>.