openbsd-ports/graphics/sane-backends/pkg
2012-02-16 22:29:15 +00:00
..
DESCR Don't compile with net-snmp by default, instead create an "snmp" FLAVOR 2011-04-25 09:34:39 +00:00
PFRAG.shared Disable the gphoto2 backend which doesn't really make sense nowadays. 2011-06-16 10:14:58 +00:00
PLIST Disable the gphoto2 backend which doesn't really make sense nowadays. 2011-06-16 10:14:58 +00:00
README Extend DESCR and tweak hotplugd(8) scripts accordingly. 2012-02-16 22:29:15 +00:00
saned.rc Simplify after recent rc.subr change. 2010-12-27 14:50:22 +00:00

$OpenBSD: README,v 1.9 2012/02/16 22:29:15 ajacoutot Exp $

+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------

First read ${TRUEPREFIX}/share/doc/sane-backends/PROBLEMS.

USB
===
Since USB scanning will be handled by libusb, you need to allow the
_saned user access to the corresponding USB endpoint. To do so, find
where your scanner is attached to using `sudo usbdevs -vd` then change
the ownerships accordingly.

e.g.
Controller /dev/usb3:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x8086), rev 1.00
  uhub3
 port 1 powered
 port 2 addr 2: full speed, self powered, config 1, USB MFP(0x082f), EPSON(0x04b8), rev 1.00, iSerialNumber L83010704250947490
   ulpt0
   ugen0

$ sudo chgrp _saned /dev/ugen0.* /dev/usb3

Alternatively, hotplugd(4) attach/detach scripts can be used to automate
this.

The reason we are changing the group and not the user is that it will
allow for multi-function devices to work for both printing and scanning
(e.g. by being owned by _cups:_saned).

To preserve your changes after a system update, use rc.local(8).
e.g. for a multi-function printer/scanner add the following lines:
chown _cups:_saned /dev/ugen0.* /dev/usb1

You can then grant users direct access to the scanner by adding them to
the _saned group.

SCSI
====
SANE only supports the generic SCSI uk(4) devices.
Make sure your user account has access to the scanner device node or you
will not be able to scan.

LOCKING
=======
Some backends (like sane-plustek(5)) use a lockfile for allowing
multiple access to one scanner. If using such a backend, you must
add yourself to the _saned group or you will not be able to scan.

NETWORK
=======
By default, the saned(8) daemon runs as _saned, so you need to allow the
_saned user access to the scanner device node.
If you're planning on using the SANE network daemon (saned) with
inetd(8) as opposed to starting it standalone from the provided rc.d(8)
script, add the following line in /etc/services:
sane-port	6566/tcp	saned	# SANE network scanner daemon