Comment # 4 on bug 1208394 from Imobach Gonzalez Sosa

I will try to summarize. We have two different use-cases: Iguana and the Live
media. I will start talking about Iguana because it is the reason to introduced
our own dbus-daemon.

# The Iguana use-case

Iguana is a module that allows running containers from initrd. Iguana starts
two containers, dinstaller-backend and dinstaller-web. The network is handled
by NetworkManager, running on the host (that's an important detail).

Apart from talking to each other, the D-installer containers need to interact
with NetworkManager. So we decided to:

* Have a private dbus-daemon for D-Installer internal communication.
* Connect to the host D-Bus daemon to interact with the system (Network or any
other service we might need).

We could not use the host daemon because, from the containers, we cannot change
its configuration.

# The Live use-case

As a side effect of the previous use case, on a Live system you have three
daemon servers: system, session and d-installer (once the service is started).
If d-installer is not started, the daemon should not be there.

And yes, d-installer is meant to be used as an installer, so it is not expected
to run on a production system. However, it is available as a package -to be
included in the ISO-, so perhaps we might want to add some kind of restriction.