Russ Allbery leaves the Debian technical committee

Posted Nov 17, 2014 20:18 UTC (Mon) by rahulsundaram (subscriber, #21946)
In reply to: Russ Allbery leaves the Debian technical committee by luto
Parent article: Russ Allbery leaves the Debian technical committee

> One also wonders why systemd-resolved has a D-Bus API, when there are two well-defined standards

It gets used by other management software including but not limited to cockpit

http://cockpit-project.org/

Russ Allbery leaves the Debian technical committee

Posted Nov 17, 2014 22:17 UTC (Mon) by luto (guest, #39314) [Link] (4 responses)

I am completely unable to find cockpit's use of this D-Bus API. I looked, but I may have looked for the wrong thing.

But the existence of a program that uses an API that shouldn't exist in the first place is not a justification for the existence of the API. To the contrary: it's a reason to ask what that program is doing using that API.

I fully admit that the glibc resolver is garbage and the nsswitch thing is even worse. That's *fine* -- point any async non-caching DNS library at whatever /etc/resolv.conf says to point at, and, when /etc/resolv.conf says to use 127.0.0.1, it'll use 127.0.0.1 and do exactly the right thing.

Russ Allbery leaves the Debian technical committee

Posted Nov 17, 2014 23:53 UTC (Mon) by rahulsundaram (subscriber, #21946) [Link] (3 responses)

You know, talk to cockpit developers. Understand what they are doing and see if you find their needs useful. If you have a better way of doing it, suggest it to them. It is an open source project with public mailing lists and all that.

Russ Allbery leaves the Debian technical committee

Posted Nov 18, 2014 0:02 UTC (Tue) by luto (guest, #39314) [Link] (2 responses)

I'd be happy to do so, but can you point me at why you think that Cockpit uses systemd-resolved's D-Bus API? I see it using org.freedesktop.login1 but not org.freedesktop.resovle1.

Russ Allbery leaves the Debian technical committee

Posted Nov 18, 2014 0:10 UTC (Tue) by rahulsundaram (subscriber, #21946) [Link] (1 responses)

I answered the question more generically on why a D-Bus layer is useful. Cockpit probably hasn't gotten around to using the newer API's because it is not currently used in Fedora and cockpit developers primarily target Fedora at this point.

Russ Allbery leaves the Debian technical committee

Posted Nov 18, 2014 0:17 UTC (Tue) by luto (guest, #39314) [Link]

I think this is a case where newer != better. DNS works literally everywhere. D-Bus not so much.

It is exactly this attitude that, I think, inspires so much irritation toward systemd. If something is better, great. If something is newer and more desktoppy, that's not a good reason to say "out with the old, in with the new".

I really, really, really hope that ping never starts to use D-Bus on my system.