Patrick O'Callaghan wrote:
> On Wed, 2010-03-03 at 10:54 +, T. Horsnell wrote:
>>> That rule has moved into /lib/udev/rules.d/. And AFAIK udev reads
>> all
>>> rules in and evaluates all the matches in order. Honestly I'm not
>> an
>>> expert, so don't take this as gospel, but I'm pretty sure
On Wed, 2010-03-03 at 10:54 +, T. Horsnell wrote:
> > That rule has moved into /lib/udev/rules.d/. And AFAIK udev reads
> all
> > rules in and evaluates all the matches in order. Honestly I'm not
> an
> > expert, so don't take this as gospel, but I'm pretty sure you have
> to
> > explicitly d
Paul W. Frields wrote:
> On Thu, Feb 25, 2010 at 09:42:15AM +, T. Horsnell wrote:
>> Hi all,
>> I need to set up a custom rule to give me mode 666 on a custom USB device
>> (or on all the otherwise un-handled USB devices).
>> I used to do this (in FC9) by modifying ruleset 50-udev-default.rules
On Thu, Feb 25, 2010 at 09:42:15AM +, T. Horsnell wrote:
> Hi all,
> I need to set up a custom rule to give me mode 666 on a custom USB device
> (or on all the otherwise un-handled USB devices).
> I used to do this (in FC9) by modifying ruleset 50-udev-default.rules at
> the libusb entry (I kno
Hi all,
I need to set up a custom rule to give me mode 666 on a custom USB device
(or on all the otherwise un-handled USB devices).
I used to do this (in FC9) by modifying ruleset 50-udev-default.rules at
the libusb entry (I know this was not the 'correct' way, but I could never
understand udev eno
