5 ms·
Care to elaborate?
by gsich 8y ago
Care to elaborate?
- jcranendonk 8y agoContainerization doesn't strike me as a common feature of an init system.
- rspeer 8y agoAnd init systems are, unfortunately, not a common feature of containers so far. I really wouldn't mind seeing both of them in the same project. Both init systems and container systems are concerned with dependencies, logging, and managing the lifetime of processes, and systemd is way better at the last two than Docker, so I'm optimistic.
- dozzie 8y agoQR code generator is not a common feature of an init system, yet systemd includes one. Modern attempt at OS packaging (a.k.a. containerization) is not a weird thing in such a neighbourhood at all.
- tssva 8y agoThe systemd init system doesn't have a qrcode generator. This is typical anti-systemd FUD of trying to conflate the systemd init process and the other processes available as part of the systemd project. The separate journald log server available as part of the systemd project can generate qrcodes. journald can cryptographically sign logs so that future log tampering can be detected. This requires two keys, a sealing key and a verification key. The verification key must be stored off server. When the keys are generated systemd can display a qrcode to allow easy recording of the verification key.
- gsich 8y agoIt seems some people on HN love to hate sytemd. Even though they can't come up with an alternative that's better. Hint: It's not sysvinit.
- inferiorhuman 8y agoHint: both sysvinit and BSD init are better. They are more mature, have fewer moving parts, are easier to debug without specialized tools, and are better understood. Plus the decoupled nature of init systems reap bonuses for system stability (unlike systemd). Having a QR code parser as part of something that's tangentially related to the init system in concept but deeply embedded into systemd in practice is exactly what the post you were replying to is complainig about. It's unnecessarily complex.
- gsich 8y agoThey are not. >They are more mature what does that even mean? that they are older? Similar to "modern XYZ" this phrase doesn't mean anything. You seem to repeat what other people say like the "QR code" without even looking it up.
- inferiorhuman 8y ago> They are not. https://stackoverflow.com/questions/32924335/using-systemd-without-journal https://stackoverflow.com/questions/32924335/using-systemd-w... > The journal is the only mandatory component of systemd outside PID1. Seems pretty deeply embedded to me. > what does that even mean? that they are older? They are older, better understood, and there are fewer substantive bugs (e.g. malformed blob = run service as root). > You seem to repeat what other people say like the "QR code" without even looking it up. https://lists.fedoraproject.org/pipermail/devel/2012-October/172163.html https://lists.fedoraproject.org/pipermail/devel/2012-October... Not sure what else you're doing with a QR library, except maybe building tetris (which seems like a bad idea for something purported to be an init system).
- gsich 8y ago>They are older, better understood, and there are fewer substantive bugs (e.g. malformed blob = run service as root). You used the same argument ("They are more mature") again. It's still not saying anything.
- deleted 8y ago[deleted]
- pseudalopex 8y agoI mostly like systemd, but judging the project as an init system with a bunch of other functionality tacked on is completely fair. The init daemon requires the logging daemon and vice versa, so they aren't really separate.
- dozzie 8y agoAh yes, this totally separate journald that you can replace with something else, except that you cannot, you can only run it in forwarding mode beside other logging daemon. Very modular. Totally not a part of an init system.
- xyzzyz 8y agoSystemd is more than simply init system and has been that since it’s beginnings.
- emmelaich 8y agoProcesses are though. And a container is just a bunch of processes. Or maybe one.