Hi Sarvi,
This sounds like Upstart is proposing a hard dependendency on D-Bus. Is
this really necessary. Has the impact on small/embedded platforms been
considered.
please lets not have this discussion again. D-Bus is perfectly fine for
embedded systems. Actually having more than one IPC is
Hi Matthias,
This sounds like Upstart is proposing a hard dependendency on D-Bus.
It proposes a hard dependency on the d-bus library and protocol.
(There needs to be *some* way of talking to init ... and the d-bus
protocol seems to be reasonably sane for doing this kind of thing)
this
Hi Garrett,
Hm, I'd actually prefer somehow, if core tools, like
initctl/runlevel/telinit etc would talk to upstart directly without
the need of a running dbus system bus.
Any particular reason?
- Someone deletes his dbus job file.
- dbus-daemon fails to start (misconfiguration,
Hi Sarvi,
Its high time we stepped up a layer from plain Unix domain sockets and
talked a higher level API. And I agree D-Bus is very likely the
equivalent 'Unix Domain Sockets' for this purpose. But unfortunatley its
not there yet. All this means is that D-Bus needs some more time to
mature
Hi Sarvi,
But that said, D-Bus is a fine choice for now. I hope though, the
Upstart community is open to code contributions from us that
allow for
modular alternatives to D-Bus. Ofcourse without compromising on
performance or clean code.
I think that Scott and I explained that
