Lennart Poettering

Hey, lazy web. Together with AWS and Microsoft, we are working on adding some minimal, native IMDS support to systemd, given how ubiquitous the concept is in the cloud world these days. It's supposed to be fully automatic, and reasonably generic. i.e. all the cloud-specific info (i.e. how to detect the clouds, which URLs to use) are placed in systemd's hwdb database, so that the code itself can be kept generic.

Right now the PR I prepped for this supports 5 major clouds. And I need your help…

6️⃣ Here's the 6th post highlighting key new features of the upcoming v260 release of systemd. #systemd260 #systemd

One of the now-standard files that systemd introduces is the /usr/lib/os-release file. It contains various fields with meta information on the OS and the OS image your system is running.

One of the fields in there is PRETTY_NAME= which contains the primary name of the OS for human consumption. It's a bit limited in some ways however. Given this is written…

5️⃣ Here's the 5th post highlighting key new features of the upcoming v260 release of systemd. #systemd260 #systemd

One of the fundamental operations one can execute on a systemd service is "reload", i.e. asking the service to reload its configuration, for example via "systemctl reload foobar.service". What precisely this triggers in the service code, is up to the developers to decide, but the assumption is that it rescans and parses its configuration files, without any interruptions…

2️⃣ Here's the 2nd post highlighting key new features of the upcoming v260 release of systemd. #systemd260 #systemd

systemd is adopting the IPC system in more and more places. One nice thing about Varlink is that it is conceptually close to HTTP, in its request/response semantics. This is on purpose to make bridging the web world and the low-level system world easy.

@michaelvogt@mastodon.social has beeing working on a Varlink/HTTP bridge in Rust, with various bells and whistles, including…

It's that time again! The systemd v260 release is coming closer. Let's restart the "what's new" series of posts for this iteration! Hence:

1️⃣ Here's the 1st post highlighting key new features of the upcoming v260 release of systemd. #systemd260 #systemd

In v259 we introduced the concept of "NvPCRs", i.e. additional TPM PCRs, that are implemented based on TPM NV Indexes in PCR mode, rather than true PCRs. PCRs are scarce, and this relieves the pressure a bit (not too much though, NV index…

Here's the third published video of my FOSDEM talks, about the Varlink IPC system:

https://video.fosdem.org/2026/ub2147/NFNKEK-varlink-ipc-system-keynote.av1.webm

This was the last one of the three. Enjoy!

#systemd #fosdem #fosdem2026

Here's the first published video of my FOSDEM talks, about native OCI support in systemd:

https://video.fosdem.org/2026/ua2118/ZKKQWC-native_oci_container_support_in_systemd.av1.webm

two more to come, stay tuned.

#systemd #fosdem #fosdem2026

I don't often share Phoronix articles, but this one I will:

https://www.phoronix.com/news/Amutable

RE: @amutable@mastodon.social

Today, we announce Amutable, our ✨ new ✨ company. We – @blixtra@hachyderm.io, @brauner@mastodon.social, @davidstrauss@mastodon.social, @rodrigo_rata@mastodon.social, @michaelvogt@mastodon.social, @pothos@fosstodon.org, @zbyszek@fosstodon.org, @daandemeyer@mastodon.social, @cyphar@mastodon.social, @jrocha@floss.social and yours truly – are building the 🚀 next generation of Linux systems, with integrity, determinism, and verification – every step of the way.

→ https://amutable.com/blog/introducing-amutable ←

#amutable #linux #systemd #⊼mutable #integrity

Right on time to coincide with the end of the year I finished my #systemd259 series of posts. And I now also prepped a blog story linking to every single one of them here:

https://0pointer.net/blog/mastodon-stories-for-systemd-v259.html

Make sure to stay tuned for the #systemd260 series, most likely starting already in a few weeks!

Also, happy new year! 🎇