On Tue, Dec 22, 2009 at 7:40 PM, Chris Frey <cdf...@foursquare.net> wrote:
> On Sat, Dec 19, 2009 at 01:15:06AM -0700, Nathanael Noblet wrote: > > > http://sourceforge.net/mailarchive/message.php?msg_name=20090630093818.GA31202%40foursquare.net > > Thanks! Yep, that's the June 30 thread. Good, we're on the same page. :-) > > > > In anycase, it works, I just need to fix the permissions and I'm not sure > > why. No rush if you are busy, but if you have any ideas, that'd be great > too > > ;)... > > You might try finding what permissions are currently being set. Try > plugging > your device, and as root, running: > > strace -e trace=open bidentify > > This should show a bunch of open() calls, opening files like > /dev/bus/usb/001/001 or maybe under /sys or /proc. > > Match that against the bus & device number in 'lsusb''s output: > > Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 001 Device 004: ID 0fca:0004 Research In Motion, Ltd. > Bus 001 Device 003: ID 0fca:0001 Research In Motion, Ltd. Blackberry > Handheld > Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > > And check the actual owner, group, and permissions on those files: > > ls -l /dev/bus/usb/001 > crw rw -- root::roo > > The udev file /etc/udev/rules.d/99-blackberry-perms.rules by default > is set to use the "plugdev" group. If the device files have that > group, you can add yourself to that group and you're set. > Interesting... this file doesn't exist. If the group doesn't exist, you can create it, or change it to something > that makes sense on your system. > > In a separate universe... there's HAL: > > I suspect there have been some HAL changes in Fedora 12, so I'm hoping > that udev is all we need to fiddle with right now. But I won't know > for sure until I actually run Fedora 12 and see what HAL is actually doing. > > I know that the old ConsoleKit style of behaviour was really cool on > Fedora, but these things keep shifting under our feet, unfortunately. > > If you want to delve into the HAL stuff, the RPM also installs > /usr/share/hal/fdi/policy/10osvendor/19-blackberry-acl.fdi. > Compare that with the other ACL files in that directory, and see > if there's anything obvious that's out of whack. Maybe using the "pda" > acl set is not a good assumption anymore. Note that hal uses > getfacl/setfacl > to set permissions, though, not groups, so use those commands instead > of ls. > > Good luck. Let us know if you run into roadblocks. > I've downloaded your 0.16 src.rpm file and built for F12. However when I do so, usb-storage grabs the device I think before barry can... so it doesn't show up in btool -l or lsusb?
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
