libftdi Archives

Subject: RE: Permissions issues?

From: "Michael Plante" <michael.plante@xxxxxxxxx>
To: <libftdi@xxxxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 7 Aug 2009 20:38:21 -0500
sys-fs/udev-124-r2, which I have installed, does appear to have some such
rules:

e.g., 30-kernel-compat.rules:

# needed for kernels <2.6.22
SUBSYSTEM=="usb_device", PROGRAM="/bin/sh -c 'K=%k; K=$${K#usbdev}; printf
bus/usb/%%03i/%%03i $${K%%%%.*} $${K#*.}'", NAME="%c", GROUP="usb",
MODE="0664"


65-permissions.rules:

SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", GROUP="usb", MODE="664"


Are either of those on your system?  (I usually access these devices as
root, so no guarantees that my setup even works)

Michael


-----Original Message-----
From: jcwren@xxxxxxxxx [mailto:jcwren@xxxxxxxxx]On Behalf Of J.C. Wren
Sent: Friday, August 07, 2009 8:30 PM
To: libftdi@xxxxxxxxxxxxxxxxxxxxxxx
Subject: Re: Permissions issues?


Xiaofan,


It's Gentoo.  I'm not seeing any rules that use 'GROUP="usb"', however.


--jc


On Fri, Aug 7, 2009 at 9:26 PM, Xiaofan Chen <xiaofanc@xxxxxxxxx> wrote:

On Sat, Aug 8, 2009 at 9:24 AM, J.C. Wren<jcwren@xxxxxxxxxx> wrote:
> What's odd/wrong is that /dev/bus/usb/002/003 is owned by root, and in the
> usb group.  Shouldn't udev be putting it in the plugdev group?  Adding
> myself to the usb group fixed the problem, but I'd prefer to understand
what
> I'm doing wrong or incorrectly expecting udev to do.


Which means your udev rule is not really executed but another system
provided udev rulle has precedence than yours.

What is your distro?

--
Xiaofan http://mcuee.blogspot.com


--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx







libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx

=


--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx   

Current Thread