On Sat, 18 Jan 2003 12:09:15 +0200 (SAST) Buchan Milne <[EMAIL PROTECTED]> wrote:
> > > Only thing to decide on is how to handle the /etc/services entry, > > > and handling of device permissions ... > > > > Maybe add saned to the usb or users group? > > Among others ... > > Hack on /etc/security/console.perms: > <console> 0660 <scanner> 0660 root.usb > > And run 'pam_console_apply -r' as root. Thank you. For my usb scanner, I have it working when I am member of the usb group, and have: <console> 0600 <scanner> 0660 root.usb According to the sane-usb and sane-scsi it is recommended to make a scanner group. I'm not sure if that's really necessary, actually, I can't think of a real reason for it. Another thing, in /etc/security/console.perms /dev/scanner is part of the <scanner> class. That should only be used for scsi scanners, and then be a symlink to /dev/sgx. So maybe that shouldn't be there. A scsi scanner is spoken to through a /dev/sgx device, which is part of the <burner> class. Adding saned to group cdwriter, would make that function right, right? I wouldn't know how to see if a /dev/sgx device is a scsi scanner or another scsi disk (maybe scannerdrake can?) so therefore I think a scanner group will not be usefull. Just use cdwriter. What do you think? For parport scanners, most of them use ppdev to make them accessible to users, but will be ported to libieee1284. I'm not sure how to handle them. > I think that's all that is necessary for usb scanners. A similar thing > would need to be done for scsi scanners. Might also need to hack on > /etc/devfsd.conf or the scanner script referenced there ... In /etc/devfsd.conf there's nothing about usbscanners, or sg devices. You mean /etc/dynamic/scripts/scanner.script? Hum, I don't even understand what it does. :-) About the sane specfile. There are a lot of configfiles under /etc/sane.d. Putting saned.conf in a saned subpackage will have the effect that all the other .conf files need to be listed all instead of just a *. Great :-) -- Marcel Pol
