And I'm daring to make a bold statement: This seems to me that here #systemd actually enhances and helps with the application of the #UnixPhilosophy of using a modular design with multiple, small services and interconnecting them.
By creating reliable connections between them. Or if some connection breaks unrecoverably to properly propagate this to all affected users. And by using a simple, short, descriptive, non-programmatic language for service files.
I have to say, I'm getting more comfortable with #systemd services. And I find it fascinating how with its templates and powerful dependency feature I could achieve some wild, very dynamic stacking of @gstreamer, @pipewire, #mpd, #mpv and #SAP / #RFC2974 with only a few lines for various systemd services. So for instance a #multicast SAP announcement of @schenklradio will only appear if something plays on that pipewire device, which only happens if that radio is on air and reachable.
Proving Lennart Poettering wrong is what drives innovation.
I've been looking into hardening systemd and I'm curious why so many units are not hardened by default. Like why isn't it a standard practice to harden systemd units? Do the exposed parts shown in the output of `systemd analyze security <unit>` have that much of an impact on the overall security of the unit? I would think these exposure points would add up to a vulnerability that shouldn't be neglected.
https://blog.sergeantbiggs.net/posts/hardening-applications-with-systemd/
I think I'm nearly ready to release the first version of wpm - a process manager for #Windows inspired by my experiences using #systemd and #NixOS, written in #Rust
Setting up custom desktop environments and complex local development environments on Windows is about to get a whole lot easier - goodbye Docker!
@schenklradio @ffhl @videolan @tokudan entweder muss ich mir vll. noch was mit #systemd basteln, dass das nicht per #SAP (#RFC2974) announced wird, wenn gerade keine Sendung läuft. Weil so ist es außerhalb der Sendezeiten dann komplett still, wenn man's auswählt, was Leute verwirren könnte. Oder gibt es zufällig alternativ sonst noch einen Zwischeneinspieler? Hatte letzten Samstag zum ersten mal reingehört und das klang so, als ob es da am Ende was voraufgezeichnetes gab?
To download the latest web Remote Extension Host of #VSCodium
https://github.com/gbraad-devenv/fedora/issues/77#issuecomment-2781339941
and to run with #systemd:
https://github.com/gbraad-vscode/code-systemd/issues/2#issuecomment-2781345108
After this, you can open http://[ipaddress]:8000
Note: if you want to restrict this, you can modify the service to bind to only host 127.0.0.1 or something like your Tailscale IP address.
I just found this website about systemd: https://systemd-by-example.com/
It's a teaching website and playground to learn how to do dependency management with systemd units.
You can follow the instructions locally with a podman container or play with how the example systemd units interact on the website.
makadamia:~ # mount -o bind / /mnt
makadamia:~ # mount -o bind / /mnt
Broadcast message from systemd-journald@makadamia (Sat 2025-04-05 22:32:53 CEST):
#systemd[1]: Caught <ABRT>, from our own process.
Broadcast message from systemd-journald@makadamia (Sat 2025-04-05 22:32:53 CEST):
systemd[1]: Freezing execution.
@pid_eins I can imagine why it happens. But is it expected? Or should it be handled more gracefully?
I added a few options to my #systemd extension for VSCode; it can switch between user services and system, allows you to group by status, enable/disable, mask/unmask, etc.
I hope to add more detailed information, like if the service is masked, units other than 'services', etc. Hope to get some more time soon, but currently on a short leave.
Thanks for the kind words and support.
@VildaVedo používal jsem pro sekundární SIMku #OnePlus6 (ještě tam mám nainstalovaný build bez systemd). Všechno mi fungovalo OK, ale např. budíček jsem na něm nepoužíval.
Dneska máme #systemd (takže budíčky by měli být OK) a dvě ze tří kamer fungují, takže už není moc co řešit ohledně daily-use.
Co se týká volání za mě to bylo OK, ale občas lidi zmiňují, že po několika hovorech klesne kvalita.
Myslím si, že pro lidi jako jsme my je to už 95% ready, pro běžného uživatele tak 50% ready.
@unix_discussions great, just what the world needed—systemd with extra portability! Now BSD users can finally experience the joy of debugging 500+ services they never asked for. Truly, a victory for freedom!
#linux
#unix
#systemd
#bsd
InitWare, a portable systemd fork running on BSDs and Linux
https://github.com/InitWare/InitWare
Discussions: https://discu.eu/q/https://github.com/InitWare/InitWare
While practising my #kubernetes #systemd #sysext talk for #CloudNative Rejekts I constantly went over time, so I tried a radical concept: just demos, no slides.
Please find the result here: https://m.youtube.com/watch?v=Hb37wNKcZdM and let me know what you think!
InitWare, a portable systemd fork running on BSDs and Linux
I've created the first alpha release of libkirmes, a Rust and C library which provides an API to access the systemd userdb.
It will be used in our localkdc project to enrich user information of a user in our kerberos database with information from the local userdb.