2 ms·
Most sites can switch from ntpd to something else. See for instance systemd timescynd which really doesn't have a reason to exist. And changing to chronyd was
by wbl 7y ago
Most sites can switch from ntpd to something else. See for instance systemd timescynd which really doesn't have a reason to exist. And changing to chronyd was a very quick switch.
I think it is really inertia. Time synchronization goes unloved at a lot of places.
- tptacek 7y agoI don't disagree! In particular, a ground-up Rust replacement for the 20% of ntpd that everyone relies on would do a lot of good and be deployable virtually everywhere ntpd is today (Raymond proposed a Go rewrite --- I strongly prefer Go to Rust, but Go has a garbage-collected runtime). But that's besides the point. Pushing a hostile fork of a popular project, raising money for it, and then abandoning the codebase entirely for a rewrite takes a "special" kind of chutzpah.
- dfrage 7y ago> Pushing a hostile fork of a popular project, raising money for it, and then abandoning the codebase entirely for a rewrite takes a "special" kind of chutzpah. Now you're just straight up lying, and contradicting your previous comment: https://news.ycombinator.com/item?id=20196474 https://news.ycombinator.com/item?id=20196474 "Raymond was openly discussing rewriting the whole thing in Go". As you yourself said, he discussed the concept of rewriting it in Go, as I recall while he was learning the language for reposurgeon. But check the repository: https://gitlab.com/NTPsec/ntpsec https://gitlab.com/NTPsec/ntpsec There's not a single .go file in it. 153 .c files, though. Today I Learned intellectual curiosity, and blogging about your work as others in this discussion have been saying is a necessity, are mortal sins.