- Debian has sent patches upstream- Mageia is *much* smaller distribution, that packager has attended *various* systemd hackfests- Mageia package maintainer sent various patches upstream- Patches are *not* accepted based on how many people you represent or which company you work for (e.g. some Red Hat dude got a "no" during hackfest before FOSDEM)
Glad to hear that! :)
QR codes is optional Built-in HTTP server is optionalBinary logging - yeah, it logs stuff. Calling logging functionality in aprogram which is meant to log things is a bit much.
It's not just "calling logging functionality", it's "running an own logging daemon" that supports a lot of other things. "calling logging functionality" is syslog(3) or maybe even printf(3) :))) and it should be enough for software that just "logs stuff". :)
You cannot separate it, if you look at status output of a service it'll
use the journal to give you useful output. Splitting things has
sideeffects. If the gain is uncertain of vague ("I don't like it" /
"UNIX philosophy"), then IMO time to trust the package maintainer.
Of course it has side effects! That's why people call it monolithic and that's why it needs some decoupling. Do you agree that a modular program is generally better than a non-modular one?
And yes, I can't say how much I don't like Windows-like ideas of binary logs / binary configs / unified registry and etc. Yeah, yeah, I know there are no binary configs in systemd, that's just an example. :)
And it seems I'm not the only one who doesn't like it! And I'm sure that at least 50% of swear words addressed to systemd could be stopped at once if the journal was made ALSO optional. So why not just do it?...
I'm not familiar with systemd code, but since it seems Debian faces systemd becoming the default, I even want to try to make journal optional by myself... :) the downside is that I don't know if systemd developers will like it at all. :(