How to get bluez to create the /dev/rfcomm0 device [SOLVED]

binro · Last edited by binro on Mon Mar 26, 2012 8:30 am; edited 1 time in total

This used to be easy! You configured /etc/bluetooth/hci.conf and restarted the bluetooth daemon and the rfcomm device appeared. Now I have to do an "rfcomm bind <address>". How do you get this done automatically?
_________________
"Ship me somewheres east of Suez, where the best is like the worst,
Where there ain't no Ten Commandments an' a man can raise a thirst"
from "Mandalay" by Rudyard Kipling

PaulBredbury · Watchman Joined: 14 Jul 2005 Posts: 7022

udev? As a wild guess.

binro · Posted: Mon Mar 26, 2012 6:19 am Post subject:

Very possibly, I guess. But packages normally come with the necessary rules. I can see nothing happening in the syslog, so don't know what to intercept. Also, there is a complete dearth of doco about RFCOMM in the Bluez package.
_________________
"Ship me somewheres east of Suez, where the best is like the worst,
Where there ain't no Ten Commandments an' a man can raise a thirst"
from "Mandalay" by Rudyard Kipling

binro · Posted: Mon Mar 26, 2012 8:30 am Post subject:

Problem solved! There is a new service called, yes, rfcomm, which basically does a "rfcomm bind all". The only clue about this was Google turned up a Gentoo source tree commit action.

_________________
"Ship me somewheres east of Suez, where the best is like the worst,
Where there ain't no Ten Commandments an' a man can raise a thirst"
from "Mandalay" by Rudyard Kipling