The "devmode=0666" option works in trusted environments, where
you have some reason to trust all your users.
Which is of limited usefulness.
Limited to "personal" computers, sure ... ;-)
Yes. But at that point it's not a hotplug problem, hotplug is
just a tool used to solve the problem ... :)
I disagree. The hotplug support in the kernel is the tool. The hotplug
support in userspace (/sbin/hotplug) is exactly what should be solving
this.
The way it _helps_ solve the problem is by providing a hook
that applications -- gphoto, sane, etc -- can use to meet
their security policies.
It's unreasonable to expect hotplug to ship with support for
every random USB-aware application. However it's fine if
installing those apps also installs specialized agents into
/etc/hotplug/usb, which know how to satisfy the application's
requirements ... at that point it's the app solving the
problem (chmodding a file, say) by using the hook.
Maybe you're defining terms differently than I am, but in
my book a script like /etc/hotplug/usb/gphoto is part of
that application, not part of the hotplug tools. Even if
it's run because of a hotplug event report.
- Dave
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
