Arch Linux

Ok heres the situation: I plug in my uncle's new Canon Powershot IS (its not the usb storage kind of cameras - i need digikam/gtkam), and yess dmesg says its detected.. a check in /proc/bus/usb/002 (in my case) and the file exists, but digikam complains that it cant read from the device..

So after some googling, chmod 0666 /proc/bus/usb/AAA/BBB made it readable and all worked fine..
Now i want this permissions stuff to be automatically done. So i go readup some kernel documentation and i see this (Documentation/usb/proc_usb_info.txt) :

THE /proc/bus/usb/BBB/DDD FILES:
--------------------------------
Each connected USB device has one file. The BBB indicates the bus
number. The DDD indicates the device address on that bus. Both
of these numbers are assigned sequentially, and can be reused, so
you can't rely on them for stable access to devices. For example,
it's relatively common for devices to re-enumerate while they are
still connected (perhaps someone jostled their power supply, hub,
or USB cable), so a device might be 002/027 when you first connect
it and 002/048 sometime later.

and

Note that since by default these BBB/DDD files are writable only by
root, only root can write such user mode drivers. You can selectively
grant read/write permissions to other users by using "chmod". Also,
usbfs mount options such as "devmode=0666" may be helpful.


So my humble request is .. add this devmode=0666 as options to the place where you mount usbfs (rc.sysinit iirc) or provide a config variable somewhere to change the default options to usbfs mount so that non-root users dont need to fiddle soo much to just get a camera working (also I dont think any normal user would do all this stuff for such a simple task).


PS: Sorry for the long description.. thought some ppl might need proof :D