> > > Ref bluez-4.43 /etc/udev/bluetooth.rules: > > > > > > # Run helper every time a Bluetooth device appears > > > # On remove actions, bluetoothd should go away by itself > > > ACTION=="add", SUBSYSTEM=="bluetooth", RUN+="/usr/sbin/bluetoothd --udev" > > > > > > Shouldn't this be of the format /etc/udev/rules.d/xx-bluetooth.rules so that it starts in the correct order - i.e. after dbus? > > > > > > Is it possible to have a udev rule check that dbus is running before executing? > > > > you are right. I should have fixed this. Just forgot about it. What > > number prefix do we want for Bluetooth. > > You don't need the prefix. D-Bus isn't started through udev... we don't need it, but we should be nice and add it anyway. I pushed a fix for that. BlueZ being the only project not following conventions here is a bad idea. > Using /etc/udev/rules.d/97-bluetooth with bluez-4.43 does indeed load all required > modules and start bluetoothd as soon as I use the hardware switch to enable Bluetooth > > Thanks, John -- 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
