5 ms·
This is, of course, more of a fun joke. More seriously, it would be great to have the good parts of systemd (logind, ability to control containers, the runner
by nine_k 5y ago
This is, of course, more of a fun joke.
More seriously, it would be great to have the good parts of systemd (logind, ability to control containers, the runner of unit files) implemented independently and without the "invasive" parts like control of DNS or binary logging.
- BikiniPrince 5y agoReverting to a different resolver isn’t difficult on something like Fedora and even manually editing on other distributions wouldn’t be that bad. Logging is a per application basis and I’ve found most things easily support syslog. So, both wishes granted.
- lavabiopsy 5y agoIt is trivial to disable systemd-resolved on any distribution, as well as making systemd-journald disable its logging to forward everything to syslog. I wonder what the GP post's difficulty was?
- glitchcrab 5y agoJust the usual gripes about systemd which get perpetuated by people who don't bother understanding the thing they're annoyed about. Sadly you could say the same thing about pretty much any topic on the internet these days.
- drran 5y ago> who don't bother understanding the thing they're annoyed about This is the root cause of the problem. Regular initd + rc scripts are simple enough to be understood by everybody, which systemd is too complex to understand in the limited time we have. There is no "systemd senior developer" or "systemd solutions architect" positions for systemd developers, to adjust investment into systemd ecosystem. We can easily replace initd by something much more powerful, like perl, javascript, python, java + spring, Emacs, or even Firefox or Eclipse in headless mode. They all are able to read configuration files and launch new processes. But (almost) nobody does so, because they are hard to debug and have very large surface.
- lavabiopsy 5y ago>Regular initd + rc scripts are simple enough to be understood by everybody, which systemd is too complex to understand in the limited time we have On a modern distro, I wouldn't say so, there is so much you would need to add on top of an rc script to get it to work correctly. Once you start trying to make use of the same capabilities it becomes just as complex as systemd, if not moreso. This is beyond just turning it into perl or javascript, I'm talking about OS-level features: for example even a basic Linux feature like mount namespaces is non-trival to do in an rc script and have everything get mounted and cleaned up correctly with all the right settings, whereas this is one or two lines in a systemd unit, and you know it's always going to work. It doesn't help much if you implement it in a shell script or in python versus having it in a systemd unit, this is code someone has to write, and if you say "it's too complex I don't understand it" then that would be limiting you because you're not using the intended security features of the OS. Does that explain it?
- kaba0 5y agoWhat is the problem with binary logging? Would you prefer the ordinary text files and the great pain of properly filtering through something like only this services’ output, from this date to that, only warnings, etc? But that is only one part, what about the performance/stability of the whole thing? Afaik continuously appending to a file is not the greatest thing, especially if you have to move files around from time to time. It’s also not like journald uses some secret format.
- withinboredom 5y agoOne problem I can think of with binary logging would be catastrophe. I have had to pull HDs, go through the logs, line by line and piece together what happened in those final moments. Text logs are easy to get at, I don’t need a special program to read, I just need something to display a raw byte on the screen. Also, I wonder what the actual performance benefits are. I remember back when most protocols were text and/or binary. Usually binary was slower when messing about with stringy stuff. For example, using memcached to cache strings. Why encode/decode strings in a binary protocol when you can just use strings all the way down? I don’t know if that premise is still true, but for us older people, it makes sense to keep inherently stringy stuff stringy to avoid overhead.
- lavabiopsy 5y ago>Text logs are easy to get at, I don’t need a special program to read I've seen this type of comment a lot on reddit and I don't understand why people say this. You do not really need a special program to read the systemd logs either, in the event that journalctl doesn't work you can easily use `strings` to read the logs. Feel free to try it right now just for fun, the binary format of journald is actually extremely simple and well-documented and just stores the logs sequentially, it's not "encoding" the strings at all. Why would it need to? It's all fulltext data.
- kaba0 5y agoRe the failure part: you can just plug in any USB stick with a normal linux distro and it will read it out just fine. Re performance: Strings are most defintely worse than some fixed size format. It’s not an accident that FPGAs were used to serialize/deserialize XMLs, why Google made a whole new binary protocol, etc. Just think about it, you have to parse a string character by character (yeah some clever vector magic can make some string processing go a few chars at a time), while a binary format with fixed layout will be practically random access. You can query the nth entry, etc.
- emersion 5y agologind has a replacement: https://git.sr.ht/~kennylevinsen/seatd/ https://git.sr.ht/~kennylevinsen/seatd/
- morganvachon 5y agoelogind has been successfully used as a drop-in replacement for logind on systemd-less distros as well. https://github.com/elogind/elogind https://github.com/elogind/elogind
- nine_k 5y agoPlease note that elogind is literally logind amended to run standalone. (I run it as a part of my Void Linux desktop.)
- morganvachon 5y agoCorrect, it's one of the few good things (in my opinion) to come out of systemd as a whole. It's a valiant effort, and I also use it in Void.
- mikepurvis 5y agoIMO there's a huge gap for an init that does process management in a container using systemd files without needing the SYS_ADMIN privilege. I've wanted this for some scenarios where I'm bridging the gap between VM/OVAs and containers, and would like a single rootfs to be able to serve in both capacities. Basically all the current options are not great: * Make invasive changes to move the container-relevant stuff to another init system. * Make invasive changes to run a systemd instance in user mode in the container. * Run the container as privileged. * Something something podman (not an option for k8s).