[d older] > In all case re-running /etc/init.d/bluetooth start does create the > /dev/rfcomm0 device.
Sound like a race condition triggered by the introduction of async kernel events. The actors might be udev and bluetooth. Does it help to add 'sleep 1' or something like that at the start of the bluetooth script. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
