#til the bad way that, at least on #debian unstable, launching a long running process in #screen (but #tmux and nohup and other seem to also be impacted) is not enough to survive a session logout, seemingly because #systemd changed something more than 6y ago and now you have to mark users as linger-able to keep the feature working. Stay tuned.
Another day, another wird issue with #systemd.
Why exactly does it overwrite almost all Environment variables within transient user service units that are automatically created when the KDE Plasma gui starts an application?
And why does bash not execute the profile script to overwrite the passed in "PATH" value?
Also funny remmina has an autostart unit, the first time it starts it has the correct environment vars, but when you close and reopen it it now has the wrong ones because of this.
@mcc @dalias @whitequark @becomethewaifu
It didn't replace van Smoorenberg init+rc. It replaced Upstart. The existence of Upstart is the part of history that many people forget or gloss over.
van Smoorenberg init+rc always was a straw man. The Debian committee included it, but everyone acknowledged at the time that the main contenders were systemd, Upstart, and OpenRC.
@mcc @dalias @whitequark @becomethewaifu
Changing compiler is not the problem. But changing the standard library becomes one. systemd gained problems with #musl because of this.
Manage Linux Systemd Services Easily With Systemd-manager-tui #systemd #rust #systemctl #journalctl #linux #tui #opensource
https://ostechnix.com/manage-linux-systemd-services-with-systemd-manager-tui/
systemd-lsp is designed to simplify the editing of #systemd Unit files by providing validation, autocompletion, and formatting features commonly available for modern languages and file formats.
@CursedSilicon @gettie mostly because #systemD (and it's competitiors) took all the right lessions:
And basically everyone (#OpenRC, #Upstart, etc. Even #LaunchD [the #init for #macOS that is literally the SystemD but before SystemD and by Apple] and #SMF [#Sun's SystemD for #Solaris] did that to allow for boot times in secinds, not minutes…
@CursedSilicon @gettie Eeyupp!
Same as with #SystemD: Shit's more dynamic and we can't sell people systems with #SysVinit startup speeds in the minutes like in 2007.
https://www.youtube.com/watch?v=o_AIw9bGogo
Noone would've started either project if the preceding solutions were "fine". Cuz they weren't!
@CursedSilicon @tilton and whilst at it, get gnomewithoutsystemd.org
and forward it to that post subheading saying "Consider using #systemD"...
https://blogs.gnome.org/adrianvovk/2025/06/10/gnome-systemd-dependencies/
This is how I manage services on arch btw
**systemd-manager-tui** — Manage systemd services in the terminal.
View logs, properties, list services, start, stop etc.
Written in Rust & built with @ratatui_rs
#UnpopularOpinion / #HotTake: I think it's the right call for @gnome to "Stop being a mad scientist" and simply offload a lot of [quite security-critical] stuff onto #SystemD.
Tho @BrodieOnLinux is wrong re: "Linux is #Unix" because technically #macOS (if we take in any #POSIX-esque system into account)!
Also shoutout to this entiled POS that decided to vomit his unwanted hatemail into the mentions before being the biggest coward I've seen since Ro!
Your cowardice is a disgrace for the fediverse and yet another piece of evidence that all the clichees of #SystemDhaters & #WaylandHaters are not exaggerated but true!
@mrmasterkeyboard @cesarpose I mean, #Xorg - like #SysVinit - both have severe issues that just ain't gonna be addressable under reasonable expectations re: hardware support, compatibility and software support.
https://www.youtube.com/watch?v=o_AIw9bGogo
There is no "#conspiracy" of #BigTech wanting to kill #X11 or even sabotage #Xlibre for that matter. It's just that some folks have trouble letting go and acknowledge that #Xserver is kept on "life support" as #Xwayland so people can run their 25+ year old #Windows games in #Wine without going apeshit.