3 ms·
What I take away from the link is: > Distributions usually have a full NTP client installed by default, why > should GNOME try to enable/disable an SNTP cl
by AdieuToLogic 11y ago
What I take away from the link is:
> Distributions usually have a full NTP client installed by default, why
> should GNOME try to enable/disable an SNTP client that happens to be
> distributed with systemd?
Well, "usually" means right *now*, little else.
And:
> > This is really about being a *client*, and
> > not trying to outsmart servers.
>
> Outsmart servers how exactly?
By not trusting them...
To me, this provides insight into Poettering's mindset of systemd creating a fool's paradise[1] regarding coexistence with anything outside of its walled garden[2]. For an example supporting this, the not-too-subtle hint of system clients outside the systemd ecosphere (NTP in this quote) being slated for elimination in distributions should be sufficient.
BTW, love your use of the phrase "interesting reasoning".
1 - http://www.phrases.org.uk/meanings/138800.html http://www.phrases.org.uk/meanings/138800.html
2 - https://en.wikipedia.org/wiki/Closed_platform https://en.wikipedia.org/wiki/Closed_platform
- digi_owl 11y agoPoettering's projects has basically turned into lightning rods for a group of devs that want Linux to have a one true way to do everything, as they see the bazaar way of doing things as a failure and something that is holding Linux back from wider adoption.
- pessimizer 11y agoLinux is widely adopted.
- digi_owl 11y agoYou know it, i know it, but as best i can tell they don't see it as "wide enough". Damn it, GregKH has basically admitted that one big reason for pushing kdbus is that the automobile industry wants to adopt embedded Linux as a replacement for QNX. And for some oddball reason they have adopted dbus as their replacement for whatever QNX RPC they used before. Except that said QNX RPC was higher performing than current dbus, in part because it was in kernel...