Re: [Bluez-users] rfcomm hell

[Marcel Holtmann <marcel@holtmann.org>]

Hi Stefan,

> > I found what was wrong, and it was udev.
> > After following a tutorial I added the following rule to change the permissions upon dev creation:
> > 
> > # cat /etc/udev/rules.d/10-udev.rules 
> > KERNEL="rfcomm[0-9]*", NAME="bluetooth/%k", GROUP="users", MODE="0660"
> > 
> > after commenting it rfcomm started connecting :-D
> 
> i have
> root@susi:/tmp# cat /etc/udev/rules.d/47-rfcomm.rules
> # udev-rules for rfcomm devices
> KERNEL=="rfcomm*", NAME="%k" GROUP="uucp" MODE="0660" OPTIONS="resmgr"

these should be needed at all. The rfcommX devices are TTYs and a

	SUBSYSTEM=="tty", GROUP="dialout"

or similar should take care of the correct permissions and group
assignment.

> The OPTIONS=resmgr is probably SUSE specific, but the rest should be generic
> and works just fine for me.

Yes, it is.

Regards

Marcel



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users