Hi Marcel, > Another question, also related to packaging: > > How should the bluetoothd be started nowadays? > > dbus-activation with a service-file like this one? > root@stoetzler:~# cat /usr/share/dbus-1/system-services/org.bluez.service > [D-BUS Service] > Name=org.bluez > Exec=/etc/init.d/bluetooth start > User=root > > But then, who will start it before XDM fires up? Has anybody already hacked up > a nice way to just start it on adapter hotplug? Some HAL magic maybe? > > I had that old udev rule hack that would call the init script at adapter > plugin, but that's ugly and racy (because it typically starts before DBus is > started). > > Any innovative ideas? we had the discussion for Fedora and we want to start it via udev, however then we need D-Bus before udev runs and that is not an option right now. So the current solution is to just do it via init.d, but in the future we want udev. The D-Bus service activation is nice, but makes problems when you wanna use the mouse and keyboard early. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
