[RFC] Common activation manager via external manager

Colin Walters walters at verbum.org
Wed Jan 5 08:05:13 PST 2011

On Mon, Jan 3, 2011 at 3:28 PM, Lennart Poettering <mzqohf at 0pointer.de> wrote:

> Hence: I think it is a bad idea to pass this along with the activation
> request. if you really want to allow activation of dbus services without
> having to manually configure them in native configuration files of the
> init system, then at least do it properly: add an API to the bus driver
> to expose all activatable bus services it read with its properties, and
> include change signals and stuff. Given that the list of activatable
> services doesn't change that often simply adding a single property to
> the bus driver whith an array of structs with the service information
> should be enough.

This seems like a pretty baroque way to pacify OS vendors left which
for some unknown reason still try to support separate /usr, but sure.

So if we did that, then we'd still always try to activate through the
external service, and just pass it the bus name, right?

More information about the dbus mailing list