Hello!

NB, I'm not deeply involved in bluetooth neither dbus development,
just a "power user".  If my thoughts are wrong, just discard them.

On Mon, 08 Jan 2007 19:47:01 +0100, Johan Hedberg wrote:
> On Mon, Jan 08, 2007, Daniel Gollub wrote:
>> If the hcid would wait for the dbus daemon this wouldn't be a
>> problem. At least hcid can handle a dbus daemon restart, maybe we
>> can enhance this.
>
> Sounds like a useful feature.

Shouldn't be the contrary?  I mean, on a clean Debian etch, every
dbus-dependent service is started by dbus:
=====
root@gismo:/home/luca# ls -l /etc/dbus-1/eventd.d/
total 16
-rwxr-xr-x 1 root root 1901 2006-11-11 15:38 20hal
-rwxr-xr-x 1 root root 1091 2006-10-24 15:22 24dhcdbd
lrwxrwxrwx 1 root root   25 2007-01-07 21:53 25avahi-daemon -> \
 ../../init.d/avahi-daemon
-rwxr-xr-x 1 root root 1766 2006-11-30 22:22 25NetworkManager
-rwxr-xr-x 1 root root 1684 2006-11-30 22:22 26NetworkManagerDispatcher

root@gismo:/home/luca# invoke-rc.d dbus start
Starting system message bus: dbus.
Starting Hardware abstraction layer: hald.
Starting DHCP D-Bus daemon: dhcdbd.
Starting network connection manager: NetworkManager.
Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
Starting network events dispatcher: NetworkManagerDispatcher.

root@gismo:/home/luca#
=====

Just my 0.02€...

Thx, bye,
Gismo / Luca