Clarification on upstart-0.5 and dbus usage

[Marcel Holtmann]

Hi Matthias,

> > Actually, this is the only supported way.
> > 
> In most circumstances (i.e. on anything but limited embedded systems)
> this makes sense.

even on the limited embedded systems this makes sense. If the bus daemon
is too bloated then fix it. There is a lot of room for improvements
inside the low-level D-Bus library and even in the daemon.

Also using the D-Bus direct communication put the requirement on Upstart
to become a D-Bus server and to message dispatching. This will bloat
Upstart. So you are moving the problem from one part into another one
and not really solve it.

> > While there is another, secret, way
> 
> Well, at minimum you'd need _some_ method to tell Upstart that the dbus
> daemon has started up and may now be registered with. :-P

Why? If Upstart starts the D-Bus system bus daemon, it knows, when it is
there. Why bother with external tools.

Regards

Marcel