ow...@bugs.debian.org (Debian Bug Tracking System) writes:
> ACL are required, and that's all. ConsoleKit already requires ACL
> support and the standard Debian kernel has ACL enabled. If you don't
> use the standard kernel, now would be a good time to review your
> custom kernel configuration.
as long as they are still made optional in the kernel configuration i
don't see how they could be required by anything.
>> better approach would be to use chgrp and chmod on the device file,
>> i.e. replace RUN+="/bin/setfacl -m g:scanner:rw $env{DEVNAME}" in
>> /lib/udev/rules.d/60-libsane.rules with the appropriate calls to chgrp
>> and chmod.
>
> No, it's not a better approach. The change is intentional and fixes
> real issues. See the changelog and the associated bug reports.
at the very least you could fallback to chmod/chown if setfacl fails.
silently failing is not a good thing in general. as for the changelog,
the only thing i see is 'try using ACLs for USB scanners in an effort to
deconflict with MFP devices.' added on Wed, 16 Feb 2011 which is not
very informative.
--alex--
--
| I believe the moment is at hand when, by a paranoiac and active |
| advance of the mind, it will be possible (simultaneously with |
| automatism and other passive states) to systematize confusion |
| and thus to help to discredit completely the world of reality. |
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
