On Thu, Dec 24, 2009 at 12:39 PM, Chris Frey <cdf...@foursquare.net> wrote:
> On Wed, Dec 23, 2009 at 01:30:08PM -0700, Nathanael Noblet wrote: > > In playing around a bit more, I saw that lsusb and btool -l as a regular > > user show no trace of the blackberry whatsoever, no error message > nothing. > > However as root, lsusb shows the Rim device as well as btool -l. > > So, if I understand you correctly, you're saying that lsusb does not > list the BlackBerry as a user, only as root? > To clarify. on F12, the stock rpm has *no* udev rules file. When I take the udev rules from your sources, and place them in the rules.d folder, subsequent insertion of the blackberry no longer shows up in lsusb as a normal user or btool -l. Prior to having the rules in place, it would show up, but btool -l would get a perm denied when trying to do anything, same with bidentify and all those other syncing tools. Also, it seems that once I put those udev rules in place, the device started getting assigned the plugdev group, whereas without the udev rules, it was always root:root... So based on your two replies, I'm thinking that putting the udev rules there has now made it change the group ownership, however I need to check the ACLs ... [g...@iridium ~]$ getfacl /dev/bus/usb/001/003 getfacl: Removing leading '/' from absolute path names # file: dev/bus/usb/001/003 # owner: root # group: plugdev user::rw- group::rw- other::--- Which doesn't give me much info past what I can already see with a ls -l on the directory... I'm wondering about how to debug the HAL fdi files in F12 vs those in F11. The usb device nodes in F11 didn't change ownership or anything, but I haven't had a chance to look at what they did with respect to the ACL stuff... I should probably be filling some of this on the fedora bugzilla I guess, but I figured you'd probably know what is going on. Any other ideas?
------------------------------------------------------------------------------ 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
