We liked #systemd v258 first RC so much that we went ahead and did another one, even if everything was absolutely fine*. Go get it while supplies last!
https://github.com/systemd/systemd/releases/tag/v258-rc2
* everything was, in fact, not fine
What is Userspace Reboot or Soft Reboot in Linux? A Simple Guide for Beginners #Systemd #Userspace #Kernel #Linux #Linuxbasics #Linuxcommands #Linuxhowto
https://ostechnix.com/userspace-reboot-linux/
Hmm am I the only one who think this doesn't make much sense?
On one side, I have to make changes to network configuration using the ip utility. But then to make them persistent, I have to play with systemd-networkd stuff. The problem's that I have to learn two things. Why not have a system with which you could configure your network through the same CLI tool using the same syntax?
Not that I want to join the anti systemd train. I haven't tweaked my PC at this level before. But recently I'm doing so and I wished I didn't have to spend few hours to get the thing working. Maybe it could be good if there was a system with which you could configure networking stuff on boot using the same ip utility?
Or maybe I'm doing it the wrong way and there is a way to make changes done with ip persistent?
Any enlightening comment is welcome!
@danimo ouch, that's quite the difference - would have expected better from systemd-timesyncd
TIL `systemd-analyze security` shows your services with emojis and makes unit names clickable so you can pop open their configs right from the terminal. Who knew Linux came with built‑in emoji judges?
#Secureboot, seamless updates, and smarter system extensions: In this #oSC25 session, dive into major upcoming features like FDE+TPM in YaST2, #systemd-sysext on MicroOS, and new tools like #sndiff. A must-watch on future of openSUSE! https://youtu.be/MPMrlUj1sVA?si=bMjxsJtyIOEyqzgb
Tumbleweed brought major upgrades like #hwinfo 25, #systemd‑rpm‑macros 26, & #Amarok 3.3.0 in July. Plus enhancements to #GStreamer, #curl 8.15.0 and #nvme‑cli 2.15. Tons of new features & security fixes! #openSUSE #Linux https://news.opensuse.org/2025/08/01/tw-monthly-update-july/
»Oook, ich mach kurz nen cronjob«
Cronjob läuft nicht
»Is ja gut, ich mach’s richtig und nehm nen systemd timer«
Timer läuft.
Danach seh ich ne Mail von cron, dass der Programmname nicht gefunden wurde. Habe $PATH vergessen…
Whatever, der #systemd timer lief natürlich einfach sofort. Ich sollte nicht dieser Versuchung erliegen, dass es mit diesem legacy-Zeug schneller geht. Tut's nicht. Und Systemd ist toll!
Meine Diaspora-Migration von Debian 11 auf Debian 12 verlief eigentlich reibungslos. Nach einem Datenbank-Update konnte ich das Skript problemlos starten.
Was nicht mehr funktioniert, ist das systemd-Startskript, wenn der Parameter "-lc" in der Zeile enthalten ist:
ExecStart=/bin/bash -lc "script/server"
Ohne diesen Parameter funktioniert es einwandfrei. Zumindest dachte ich das die letzten vier Tage nach dem Update.
Heute Morgen stellte ich jedoch fest, dass Diaspora (seit meinem Beitrag gestern Abend) „hing“. Es wurden keine neuen Beiträge abgerufen und der letzte Beitrag nicht gesendet.
Nach einem manuellen Neustart scheint Diaspora wieder reibungslos zu laufen.
Jetzt frage ich mich jedoch, ob dieser „Hänger“ mit dem oben genannten Parameter zusammenhängt, was er eigentlich bedeutet und ob es einen „Ersatzparameter“ für Debian 12 gibt.
New to #mkosi-initrd? It’s more than a #dracut alternative; it’s a #dev-friendly, RPM-driven #initrd builder with future potential.
Integrated in #systemd Builds from known sources
Still maturing (arch/feature limits)
Explore the pros/cons from this #oSC25 talk https://youtu.be/p78J3Ql7D6s?si=JbKZpq9fFb3Oesr9
The #ubuntu login loop that I encountered about a month ago is caused by specifying dependencies in a systemd automount file.
The visible symptom is a GDM login loop.
Another symptom is that /tmp/.X11-unix and /tmp/.ICE-unix will be owned gdm/gdm, instead of root/root. Changing the ownership to root/root fixes the login loop, but it returns after the next reboot.
All the gory details are spelled out here.
I like to use #run0 instead of #sudo, but encounter problems, when having more than one user in the sudo group:
1. Minor, but annoying: On the shell, I always must choose which identity should be used. Can't it just assume the current login?
2. Opening a file in #Emacs with the run0 #TRAMP method hangs. Probably identity selection does not work in Emacs? Again, it would be cool, if it just took my current uid as default.
Any idea how to fix that? TIA!
Is it somehow possible to specify additional options to #journalctl's grep function?
I usually need some sort of `grep -C` for logfiles and it looks like that isn't possible using only journalctl options.
i started to understand the reasoning behind #systemd a lot more when i remembered that some people administer not just one or two (or even a dozen) linux machines, but have networks with hundreds, if not thousands, of them, and the technical/maintenance costs of any hacks that one might otherwise accept on a more traditional system multiply to become quite serious issues at that point
#Ansible and #Podman work quite well together, and there are well-supported modules for Podman pods, networks, containers, #SystemD unit creation, etc.
https://docs.ansible.com/ansible/latest/collections/containers/podman/index.html
Not sure what you mean by “doing custom script for every service”, @fedefricoo? It seems that with or without Ansible you need to explicitly specify your custom configuration for every service, so that doesn't seem to be anything special to doing it with Ansible?
Manage Linux Systemd Services Easily With Systemd-manager-tui
“Managing services on a Linux system often means typing long systemctl commands or digging through logs with journalctl. But what if you could do all that from a single, easy-to-use terminal interface? That’s where systemd-manager-tui comes in.”
...continues
See https://gadgeteer.co.za/manage-linux-systemd-services-easily-with-systemd-manager-tui/
I'm trying to figure out setting up an email (SMTP) service on my little hosted machines, so I don't need to rely on any particular mail provider.
Which leads me to thinking I really like how #Podman can generate #SystemD units to automatically manage the service containers.
And that has led me to the conclusion I probably should wait for #Debian Trixie release next month, when I can migrate past Podman 4.3.
How do you manage SMTP service for yours, @mike?
I'm sorry, but #Wayland and #Systemd are BOTH abstraction engines with boundary issues.
They even struggle against each other for control.
It's like 2 imperial bureaucrats struggling for jurisdiction over all they can with marketing minions chanting "Order", "Security", "Unity".
Predictability certainly isn't a goal, nor granular access and control.
The people will soon be answering, what's Unix? This is Linux.
Long story short, I broke my #Linux installation. Let me know if you can relate x)
