Instead of automatically starting the bluetooth subsystem when devices
are added, let's invoke a wrapper script in /lib/udev and have that
wrapper check whether /etc/rc.d/rc.bluetooth is executable first.

diff -Nur bluez-4.99/scripts/bluetooth.rules.in bluez-4.99.orig/scripts/bluetooth.rules.in
--- bluez-4.99.orig/scripts/bluetooth.rules.in	2010-10-02 18:25:27.000000000 -0500
+++ bluez-4.99/scripts/bluetooth.rules.in	2013-06-27 22:05:55.572332197 -0500
@@ -1,4 +1,4 @@
 # Run helper every time a Bluetooth device appears
 # On remove actions, bluetoothd should go away by itself
-ACTION=="add", SUBSYSTEM=="bluetooth", RUN+="@prefix@/sbin/bluetoothd --udev"
-ACTION=="change", SUBSYSTEM=="bluetooth", RUN+="@prefix@/sbin/bluetoothd --udev"
+ACTION=="add", SUBSYSTEM=="bluetooth", RUN+="/lib/udev/bluetooth.sh"
+ACTION=="change", SUBSYSTEM=="bluetooth", RUN+="/lib/udev/bluetooth.sh"