[I've CCed Marco, our udev maintainer]

Hi,

On 29.03.2012 03:47, Scott Howard wrote:
> Hello Maintainers,
> 
> USBtinyISP is a commonly available cheap programmer used with AVRs and
> avrdude [1,2]. However, the device is frequently owned by root -
> requiring to either access it as root or to provide a udev rule [3].
> Many novice users are unfamiliar with udev rules and are frustrated
> with the programmer, which is a shame since it should and can "just
> work."
> 
> What is your opinion of shipping avrdude package with that udev rule?
> Here's the one I've been using:
> 
> SUBSYSTEM=="usb", ATTR{idVendor}=="1781", ATTR{idProduct}=="0c9f",
> GROUP="dialout", MODE="0666"

Why 0666 if it's group-owned?

> It's a little different than some other ones, specifically being owned
> by the "dialout" group, which I think is appropriate. MODE can be made

I'm not sure yet, if dialout is the appropriate group for this purpose,
or if we should use another existing group, or create a new one.

The alternative would be, to just use 0666 and don't bother with group
member ships at all or use something like consolekit, which applies ACLs
for currently active users automatically (although for a programmer this
is probably not ideal)

Marco, any suggestion which group would be suitable for that or how to
deal with that gnerally?

In general, I think the idea is fine.
Given that USBtinyISP is not the only USB programmer, we'd probably need
to extend that udev rules file for new devices [1], unless there is a
way to generically detect if the attached device is a programmer.

Michael


[1]
http://www.mikrocontroller.net/articles/AVRDUDE#Aufruf_unter_Linux_als_user_.28non-root.29
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to