@maralorn I think the challenge here will be to parse the expressions in RestartSec. I.e. it can also be something like "4m 20s" even though the option name suggests something different.
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 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.
@kernellogger But if a feature is marked as deprecated, this mean that people should avoid using it. So what i don't understand is if they are undeprecating it, or just reintroduce it, because other projects ignored the deprecation (that shouldn't be how things work in an ideal world)
For the kernel it boils down to: the construct "deprecated" has not much meaning, apart from telling people to migrate away from something; what matters is Linus' "no regressions" rule[1].
Of course in reality things are more complicated and things sometimes needs to be handled on a case-by-case basis.
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
@swelljoe ah, no Ive not chosen systemd, its forced on. I do appreciate both; but ultimately I think it's only a syntax improvement, and I still hope for it's (eventual) replacement.
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??
@hyc "RAII patterns supported by all compilers that matter and used by the kernel and other major Linux projects are garbage bloat, asckchyually" is exactly the kind of elitist drivel and delusion of grandeur that I was expecting, bravo, bullseye, 9/10
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.