Hacker News new | ask | show | jobs
by throw0101a 2618 days ago
> Seems odd to praise the BSDs for developing everything in a single repo but faulting systemd for the same approach.

I think it is more accurate to say that the (supposed) problem with systemd's approach is actually tight coupling as opposed to a single repo.

OpenSSH, OpenSMTP, OpenBGPD, LibreSSL, Mandoc, the recent Unwind, etc, may all be in the same repo, but none depending on each other. Try taking systemd-resolved (or journald) and running it on its own.

If the various systemd "components" were actual components that could be swapped out for something else there would be fewer complains IMHO.

systemd-as-init-replacement is/was fine. systemd-as-kitchen-sink is where things went sideways.
1 comments
CameronNemo 2618 days ago
Chrome OS runs systemd-journald on top of Upstart. Not that such a setup is supported or encouraged.

One of my main gripes about resolved is the D-Bus interface. Lennart needs to remove his lips from that protocol's ass.

link
Spivak 2618 days ago
> Lennart needs to

And replace it with what? I genuinely don't know anything that exists right now that could replace it. Linux and ecosystem have a lot of IPC primitives but very few usable systems: I know of dbus and ip.

link