3 ms·
Then, I guess, the main Maintainer of pool.ntp.org, who explicitely stated¹ that he agrees with Lennart Poetterings reasoning also hasn't read that? It is a re
by Merovius 11y ago
Then, I guess, the main Maintainer of pool.ntp.org, who explicitely stated¹ that he agrees with Lennart Poetterings reasoning also hasn't read that?
It is a really poor signal how much crap gets flung at the systemd people for this bugreport that is
a) not even a day old
b) entirely inconsequential for anyone but the systemd devs and maybe Google
c) is apparently completely misunderstood and/or misrepresented
[¹] https://github.com/systemd/systemd/issues/437#issuecomment-117423000 https://github.com/systemd/systemd/issues/437#issuecomment-1...
- AdieuToLogic 11y agoSpeaking of misrepresenting... In the response you link, "abh" agreed about a specific point in "Poettering's reasoning": Lennarts reasons for not using *.systemd.pool.ntp.org ("systemd isn't a distribution") makes sense to me. This is very different than agreeing that hard-coding a set of NTP servers into the code base is the way to go. To this point, "abh" wrote: I'd suggest having no default NTP servers in the systemd code... Which is what many others have requested as well. If this were an isolated decision, it would be a different thing. But it is not, as several others in this thread have provided supporting evidence[1]. 1 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658
- Merovius 11y agoI am sorry if I was unclear in that. My comment (and similar comments in other threads) directly referred to criticism of Lennart for deciding that he doesn't want a vendor zone for systemd. In regards to the DNS server comment: I said it elsewhere before, this is completely unrelated. You may disagree with the decision from a political viewpoint and that is totally fine. But from a technical viewpoint the usage of the Google DNS Servers is completely reasonable.