Docker is just opinionated systemd, change my mind.
#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/
KDE Binds Itself Tightly to Systemd, Drops Support for Non-Systemd Systems
Sad to know #Linux From Scratch #LFS is dropping #SysVinit support and going #systemd only now
Linux From Scratch Abandoning SysVinit Support
Linux From Scratch Abandoning SysVinit Support
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/
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 ?
#Systemd daddy quits #Microsoft to prove #Linux can be trusted
https://www.theregister.com/2026/01/29/lennart_poettering_quits_microsoft/
OOM Killer triggering systemd-networkd restart on OCI OKE nodes (Ubuntu 24.04), causing DNS/CNI failure #networking #kernel #2404 #systemd #kubernetes
#systemd socket activation with #golang
One of the feature that macOS known for is the fast boot times. According to Wikipedia, this was achieved by using on-demand activation in launchd, the service manager for macOS.
In #Linux with systemd, we can achieve the same behaviour by using systemd.socket(5).
In this journal, we take a look on how to implement it on Go program that listen and serve HTTP.
What a fun day! I built an agent system for handling alerts on my homelab. If something pops up, it invokes a quick Claude session (headless) that investigates, proposes a solution, sends me a report on Telegram if it’s serious, and asks if I want to let it fix the problem. No more endless alert emails from Prometheus. I was getting ‘alert fatigue’.
And then, I built the cutest little monitoring panel for my important infrastructure. Tap to turn the screen on, tap again (or wait 10 minutes) to turn it off, and it will turn itself on if there are errors. This is running on a very old Pi 3B+ and a DSI 5” touchscreen (only $35!! Includes the stand!!). This was all prompted by a failing nvme drive in the proxmox node that ran my DNS. #python #systemd #sse #homelab #DNS
Everything you hate about the Linux Desktop in one single T-shirt 😂
@qwertz interop is great. Other factors are great.
The 'What’s changing?' section of Adrian Vovk's June 2025 blog post also touched upon why change was appropriate. This was eyebrow-raising:
＂… code was initially implemented for GNOME 2.24, and is starting to show its age. It has received very minimal attention in the 17 years since it was first written. …＂
<https://fosstodon.org/@AdrianVovk/114661507151392865> @AdrianVovk
– via <https://www.reddit.com/r/freebsd/comments/1l8px08/comment/mx8uqv5/>
some #linux folks look at the priorities of people like poettering and projects like #systemd and imagine some sort of conspiracy where microsoft paid him and others off to sabotage desktop linux
but really, the simpler explanation is that, as regular users don't pay for linux distros, most of the funding comes from companies paying for support, mostly big corporations with fleets of hundreds or thousands of machines that need updates, security, etc.
previously, a lot of these used to be just servers, but as linux is becoming more viable as a workstation OS, other needs become prioritized
like, say, being able to cryptographically verify that the entire OS is clean of any extraneous binaries, to make it even harder for an infiltrator to steal company data
and while it's relatively easy to do a large part of that using other techniques (create your own private key, add its public key into the trusted list, build a UKI out of the kernel and initramfs, encrypt the rest of the hard drive), that's not as viable if you're managing a thousand machines instead of just one, of if you don't trust those individual machines to store the private keys to build the UKIs out of (what if an infiltrator gains root access on one of them?), or if you want more than just the kernel and initramfs signed
heck, a large part of what systemd has been doing for the boot process was about getting that possible, but instead discussions of that were stuck on "THEY want us to use secure boot and eventually lock down the ability to disable it / replace the set of keys, so you can't change the OS on your PC!!!111"
how about instead of "big companies are paying corporate linux devs to sabotage linux", we all take the more reasonable step of "big companies are paying corporate linux devs to enable things they need" -- it's just that "things they need" now happen to include workstation usage and thus more strongly intersect with a hobbyist linux desktop experience -- after all, very few people complained that the linux kernel is still tuned way more strongly for server usage than desktop usage (because all this time the big companies paying for development were using it primarily for servers)
@qwertz I'll make this point:
― if a person likes GNOME without systemd, then the person does not really like GNOME.
Need to be realistic about the paths chosen by developers; about consensus.
When Apple took paths that I could not tolerate, I stopped using Mac OS X. And so on.
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst