I think that #systemd should do package management. I hate when I have to install some software, but it only has a .deb package. I think that a unified packaging format for Linux would be good.
#Flatpak takes a lot of space and doesn't work well with CLI software. #Snap relies on a closed backend and is not very fast.
It's been a while since we gave an update on the #postmarketOS#systemd integration, so here's an update post (and instructions on how to get involved).
I know people love hating on #systemd but there are so many things that are great about it. The journal is among the best (and the one that people seem to hate the most for reasons I find hard to relate to). Building a service with good logging is literally free, no code required, STDOUT/STDERR goes to the journal, you're done. Ingesting those logs into something like Loki is also free. #linux
From gratuitous use of superfluous language features (a cleanup handler, for a single fd, srsly?) to inappropriate use of standard POSIX APIs (using connect+write on a socket that only sends one message and then gets closed, really?) Older compilers don't even support a cleanup attribute, and this code is used as a model of portability??
Our goal is to make GNOME OS a daily driver for QA and finalize the migration, but this work will be fundamental to the future of all secure image based / immutable Linux distributions.
hmmm
systemd-oomd is so confusing, memory OOM killer doesn't work since it is not monitored...
Specified my user service as documentation said, but it is needed to perform reload-daemon to work hmmm...
echo 1 to memory.oom.group is not also possible.
Anyone has an idea to make it reload every time I sign in?
Wenn ich ehrlich bin, habe ich darüber zu wenig Ahnung. Ist dies so anzuwenden und zu empfehlen oder wie seht ihr dies?
»Systemd-Alternative zu sudo soll Linux sicherer machen:
run0 lässt reguläre Benutzer Programme mit root-Rechten ausführen. Es ähnelt sudo, nutzt aber andere Mechanismen zur Privilegienerhöhung und soll sicherer sein.«
I generally am in the ambivalent-to-in-favor-of-systemd camp, i think it's a heck of a lot nicer than the randomass init scripts we used to have to deal with, but.....
Ha. Turns out my incoherent rant about #systemd actually got a response from Lennart Poettering, which I didn't see because he's on mastodon.social.
not that it helped because he went all "that's not a systemd issue"
(sure it isn't but as I mentioned I actually solved the issue with the variables. The issue now is that the stuff still doesn't actually start because... what was it this time? It closed with an exit code? The reset counter is too high? Or something about the wrong folder?)