[systemd-devel] Running system with neither dbus, or kdbus?

[Mantas Mikulėnas]

On Fri, Feb 13, 2015 at 1:56 PM, Dimitri John Ledkov <
dimitri.j.ledkov at intel.com> wrote:

> I have a minimal system and I don't have for example policykit or
> graphical things.
>
> I don't have kdbus yet.
>
> However at the moment it seems that e.g. networkd & logind components
> require dbus system bus.
>
> Is it feasible to modify networkd/logind to operate without system
> dbus? E.g. similar how init / systemctl use /run/systemd/private for
> communication.
>
> Would such modifications be welcomed?
>

I doubt it.

Sure, if you had the time, you could patch all these daemons to create a
mess of Unix sockets, and you could patch all consumers to use those
individual sockets (yes, third-party programs call into logind as well),
and you could find all the places where DBus service names are used for
synchronization & replace them with lockfiles...

But you'd just end up reinventing DBus, *poorly*. And for what advantage?
It's just a message bus. I've seen plenty of 'minimal' systems that still
run a dbus-daemon just fine.

*(in fact it confuses me greatly that you're concerned about DBus but
happily run systemd & logind & such)*

-- 
Mantas Mikulėnas <grawity at gmail.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20150213/9e7ae731/attachment.html>