[argyllcms] Re: argyll v0.60.2 usb assignments

  >Right, so the hotplug or udev stuff isn't working. As I mentioned
  >in the doco, udev didn't work on the Redhat clone I was trying it on,
  >whereas hotplug worked perfectly. It seem then, that neither are 
  >working 
  >on some systems. If anyone tracks down what the secret is, please
  >let me know.
I had the same problem as warp_foo had. In fact this thread helped me a 
lot to solve the problem. I'm working on SUSE 10.1. On my system using 
the recommended udev-rule the device was created with a name that 
wasn't recognised. Something like /dev/usbdev4.13

A lot of trail and error later, I found out that it is possible with a 
udev-rule to change the owner/group assignment of the device as it is 
made by the system in the /dev/bus/usb subdirectories

BUS="usb", SYSFS{idVendor}="0765", SYSFS{idProduct}="d094", 
OWNER="caspar", GROUP="users"

So, no NAME="%k" argument, because that is creating a new device 
under /dev/ and none under /bus/usb/ and basically that is causing the 
problem. The MODE="%k" argument doesn't work on the system-created 
device. Looking for a solution I found the OWNER-argument, and that 
solved it.

I don't know if this is a fundamental solution, but it works for me, and 
since you asked...

Caspar.
-- 
Wij leven in een post-emotionele tijd van krokodillentranen en 
geconstrueerde emotie. --Civitas (GB 2004)

Other related posts: