Am Mittwoch, den 29.06.2005, 14:42 -0600 schrieb Dax Kelson: > http://www.gurulabs.com/goodies/Using_Linux_and_Bluetooth_DUN_with_the_Treo650.php > > Any feedback or comments are very welcome. > Hi Dax! First of all I'd like to say thanks for that excellent guide. But there's one thing I'd like to see changed and one I'm missing: First is pairing: I think we should stick with "security user". Default dbus_pin_helper doesn't work atm (see bugzilla #160676), but the normal pin_helper does. So instead of adding a _third_ helper we should just use bluepin. > # PIN helper > pin_helper /usr/bin/bluepin; > > # D-Bus PIN helper > #dbus_pin_helper; This also has the positive side effect that you don't need to disable SELinux bluetooth protection. If you use "security auto", simply "echo 1234 > /etc/bluetooth/pin" is enough, you won't need the third helper in this case ether. Second is creation of rfcomm devices. There is no /dev/recomm[0|1|2] in FC3/4 by default because of udev. Do you have a *.rules file for rfcomm or how did you get the devices? I'm no friend of udev, so I wonder what the correct way to create them is (mine is just a dirty hack). > Dax Kelson > Guru Labs > Bye Christoph
