The "Devuan" Debian fork and the fuss about systemd

I took a quick peek at its source code, and it does not seem to use ADJ_FREQUENCY. Does it really adjust the clock's frequency?

> Right now it does talk only to one NTP server at a time, so it will work best syncing against a set of local time servers that run a full NTP server implementation.

That can work for a server or desktop usecase, but it will not work as well for a laptop or similar usecase, where a "local" time server might not exist at the moment.

And even on a controlled network, there's the risk that one server has gone insane; the recommendations I have seen is to have three or four NTP servers in your network, so a NTP client can detect and ignore the falseticker.

> And there is nothing wrong with that. In fact, systemd's documentation explains how to do this.

Does it even need documentation? Do a "systemctl disable systemd-timesyncd", a "systemctl enable chrony", and you're done.