Ok #Linux nerds and neckbeards. Why does #Systemd list this (when using completion) even tho it's not existed for 10yrs on my system, is nowhere, and doesn't come up in list-units/list-unit-files.
Again, this file or pkg doesn't exist anywhere on my system and hasn't for 10 yrs. Maybe just a side effect of having a 10yr old install 
If I write systemctl status --all in the terminal I can see some writing about old units like "Unit ntpsec.service could not be found." or something like that.
So the question is, where does #systemd get it from? I haven't had ntpsec for a long time.
and there are no unit files left in the system, but for some reason systemd remembers them and searches for them for some reason, and throws an error.
ParticleOS – ein systemd-Betriebssystem
https://linuxnews.de/particleos-ein-systemd-betriebssystem/ #systemd #poettering #distributions #linux
/etc/resolv.conf with data it receives from DHCP for each connection. Removing the symlink, or pointing it to /run/NetworkManager/no-stub-resolv.conf, and then systemctl restart NetworkManager.service would do it. Maybe you also have to change /etc/NetworkManager/NetworkManager.conf before that. For details, see NetworkManager.conf manual page on options dns and rc-manager.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?
@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
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.
Just wrapped up a revamp of the #Palworld #Linux installation script for dedicated servers, now with inclusion of a management interface and Discord notification support!
https://github.com/VeraciousNetwork/Palworld-Linux
Tested on #Debian but probably works on other platforms. Management interface written in #Python and fully integrated with #Systemd
/run/systemd/resolve/resolv.conf was still there. #FOSS #systemdGood news, for me, personally . Looks like a bit of an ugly process to get there; but, it's important to see how the sausage is made I guess. 
https://salsa.debian.org/systemd-team/systemd/-/merge_requests/289
#Debian #systemd maintainer today removed both systemd-resolved and systemd-nspawn packages from Testing/Trixie/Debian 13 - soon to be in feature freeze - due to disagreements with the Technical Committee. New installs can use resolvconf. https://tracker.debian.org/news/1632477/accepted-systemd-2574-4-source-into-unstable/
