Here's the second published video of my FOSDEM talks, about VM Integrations in systemd:

https://video.fosdem.org/2026/h2213/G7VMEN-vm_integration_in_systemd.av1.webm

one more to come, stay tuned.

#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

LFS/BLFS will no longer be developing the System V versions

https://fed.brid.gy/r/https://lists.linuxfromscratch.org/sympa/arc/lfs-announce/2026-02/msg00000.html

🐧 Linux From Scratch becomes the latest victim of systemd

｢ Another reason for the decision to end System V init support was upstream software trends. And more specifically, major desktop environments, including GNOME and KDE Plasma, are increasingly introducing a hard dependency on systemd-specific functionality that is not available in System V init ｣

https://linuxiac.com/linux-from-scratch-drops-system-v-init-calls-decision-regrettable/

#lfs #systemd #opensource

Wollt ihr unter Linux eigene Dienste starten und steuern? Das geht mit Systemd-Services.

Wie Ihr Systemd-Services optimal für euch nutzt, zeigen wir euch in diesem @ct_Magazin Artikel, den ich betreuen durfte.

https://www.heise.de/ratgeber/Linux-Systemd-Services-verstehen-und-so-eigene-Dienste-steuern-11091823.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege

#Linux #LinuxSystem #Systemd #SystemdServices

LFS/BLFS will no longer be developing the System V versions https://lobste.rs/s/6xpxg9 #linux #systemd
https://lists.linuxfromscratch.org/sympa/arc/lfs-announce/2026-02/msg00000.html

Let's see where this cuts off on threads...

Using bash, python, and a systemd timer I have a check running every 5 minutes for new mastodon posts. Those posts are converted into an image and reposted to threads with a link back to my mastodon post.

I wanted to set this up for X as well, and its totally doable, but they switched new developer accounts to pay-per-use as of recently. Not ready to pay to post on X.

#x #threads #meta #mastodon #python #systemd #bash

@postmarketOS @bshah @z3ntu that's incredible! Seems like it's getting closer to becoming a daily solution? Btw. does @postmarketOS have any / its own infrastructure to manage + reduce battery usage? Or would that be something which #systemd could still implement and could be useful for (so that laptops could benefit from this, too)?

Docker is just opinionated systemd, change my mind.

#docker #systemd

You know #Nginx, #PostgreSQL, #Iptables, and #Systemd. You don't need another #AWS #tutorial. You need a translation guide. :thaenkin: 🤔

I made one: AWS concepts mapped to their traditional #Linux equivalents. Stop learning, start translating #SysAdmin #DevOps #Developers https://nskm.xyz/posts/aws-1/

@sv1sjp one thing missed on that article is #quadlet as #podman integration with #systemd.

System Deadlock #nvidia #systemd

https://askubuntu.com/q/1563538/612

KDE Binds Itself Tightly to Systemd, Drops Support for Non-Systemd Systems

https://fed.brid.gy/r/https://hackaday.com/2026/02/02/kde-binds-itself-tightly-to-systemd-drops-support-for-non-systemd-systems/

KDE Binds Itself Tightly to Systemd, Drops Support for Non-Systemd Systems https://hackaday.com/2026/02/02/kde-binds-itself-tightly-to-systemd-drops-support-for-non-systemd-systems/
#LinuxHacks #Kde #Systemd

the fact that, right now, for more and more "non-techy" people, desktop #linux and open-source software is becoming legitimately worthwhile for certain use cases is pretty much a miracle

we don't have as many skilled developers, UI designers or testers as actual big tech companies do, which is why the two major linux desktops have the problems they do: #GNOME is restricting customization and bundling #systemd dependencies to reduce the variability that they have to design and test for, #KDE #Plasma is suffering from all sorts of bugs and papercuts because their spectrum of customization makes it impossible to test for every possibility

i don't think this moment will last forever, unless both ms and apple somehow screw up even harder and actually go into serious financial trouble

which can happen, given that both are still heavily invested in "artificial intelligence", but is not a guarantee

right now, i would expect all of us to brace for the possibility that microsoft does a course correction, and makes a windows 12 that's actually more performant, less ai- and privacy-invasive and, perhaps as a bonus for gamers, works even better with the xbox game pass or some other thing they have going

or maybe they design a new version of directx that works better with new graphics hardware than vulkan

and eventually the advantage linux has in gaming will also shrink

because i remember how happy the linux community was the last time microsoft did a serious fumble like that (releasing the resource-hungry vista at a time when small low-performance "netbooks" were all the rage), but that didn't last long, either -- microsoft fixed their errors with windows 7, "netbooks" got replaced by smartphones and tablets

After a brief discussion I initiated #systemd updated their stability guarantees to be aligned with the #kernel:

"The kernel has a "don't break userspace" policy [1] which is very easy
to understand and like (even if the details are complicated). [...]

To improve public perception, and to align the docs with practice, let's
make a general promise to keep stability [...]"

It's been that way implicitly for a while and now it's communicated clearly as well.

https://github.com/systemd/systemd/commit/f4dd927e5cc47a88fa427a6e1ce210b1f2350978

Linux From Scratch reluctantly confirms a systemd-only future, ending System V init development due to mounting maintenance pressure and upstream changes.
https://linuxiac.com/linux-from-scratch-drops-system-v-init-calls-decision-regrettable/

#linux #opensource #lfs #systemd

If you had told me in, oh say, 1997-98ish I'd be an ardent user and supporter of #Linux, a monolithic kernel, now with a Explorer.exe-like #systemd bullshit, I'd have laughed your face off your skull.

Back then, we had a variety of AltOSes, running on a plethora of processors, micro kernels with truly journaled, dynamic file systems, with instant updates without reboot, a veritable zoo of GUIs and shells, all bubbling with creativity and vitality of a community full of enthusiastic users.

1/x

Can anyone look at https://github.com/systemd/systemd/commit/f5cdf95 and then https://github.com/systemd/systemd/issues/39056 and tell me that this isn't just people accidentally breaking things and then retroactively declaring it to be intentional?

In all seriousness, there was no consideration at all in the original change, and then in the bug discussion the only explanation is "that's just super weird and broken".

If people did this at work, they'd get a sit-down with their manager, no? How is this gaslighting behavior OK in #systemd ?