I think that the real problem is in install programs/methods. If we were
to use Oliver's suggestion (creating a group 'scanner'), setting the
owner of /dev/sgX to 'scanner', its permissions to 660, and the scanner
binaries to be owned by 'scanner' we'd solve a whole heap of
problems.... But even with a great install, problems remain:
- What users should be granted entrance to 'scanner' group?
- What device to set. Could be that the device changes?
I suppose that the install program could do some checking (to see if
there is a 'scanner' group already, etc), and then do a dialogue to
asking for the information from the user (with some reasonable
A well thought out install (even if it calls for later root
intervention, or even a 'scanner permissions' program) might solve a lot
of the problems we're seeing on the list with permission problems.
-- __ / ) / Bob van der Poel /--< ____/__ firstname.lastname@example.org /___/_(_) /_) http://users.uniserve.com/~bvdpoel
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail email@example.com