On Wed, 03 Jan 2007 00:18:08 +0100
"Felix E. Klee" <[email protected]> wrote:
> I've installed sane-backends-1.0.18 on a Slackware 10.2 system with
> kernel 2.6.14.4 and libusb 0.1.12. Also, I've installed the udev rules
> that are part of the sane backends, just as explained in README.linux:
>
> cp sane-backends-1.0.18/tools/udev/libsane.rules \
> /etc/udev/rules.d/50-libsane.rules
>
Hi Felix,
I created some udev-rules for certain devices on my own, mainly for two
reasons: defining a decent mount point for /etc/fstab and setting the
appropriate permissions (like 660).
Here is an example of two rules in /etc/udev/rules.d/11-udev.rules:
# creating /dev/scanner with root:scanner (I have a SCSI scanner)
BUS=="scsi", SYSFS{model}=="Astra 2200 ", NAME="scanner", GROUP="scanner"
# creating a link from /dev/sd?1 to /dev/usbdisk, which is used in /etc/fstab
with the mount point /mnt/usbdisk
BUS=="scsi", SYSFS{vendor}=="WDC WD16", NAME="%k", SYMLINK="usbdisk"
I would create a similar rule like
BUS=="usb"; SYSFS{model}=="your model goes here", NAME="scanner", GROUP"scanner"
and make sure you belong to group scanner
Cheers,
Klaus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20070103/a9e7f5ad/attachment.pgp
From [email protected] Thu Jan 4 00:12:49 2007
From: [email protected] (Felix E. Klee)
Date: Thu Jan 4 00:13:09 2007
Subject: [sane-devel] udev updates /dev/..., sane accesses /proc/...
In-Reply-To: <[email protected]>
References: <87tzz99fwv.wl%[email protected]>
<[email protected]>
Message-ID: <87mz4zaemm.wl%[email protected]>
At Wed, 3 Jan 2007 21:39:05 +0100,
Klaus Dahlke wrote:
> I created some udev-rules for certain devices on my own, mainly for
> two reasons: defining a decent mount point for /etc/fstab and setting
> the appropriate permissions (like 660).
Thanks for the reply! Certainly, creating a device node or symlink with
a fixed name is a possibility ...
> I would create a similar rule like
> BUS=="usb"; SYSFS{model}=="your model goes here", NAME="scanner",
> GROUP"scanner"
> and make sure you belong to group scanner
I could simply copy the entry for my scanner from libsane.rules and add
a NAME or SYMLINK key. In addition, I'd have to edit
"/usr/local/etc/sane.d/snapscan.conf". That's not according to the
(misleading, incorrect?) instructions in README.linux, but it should do
the trick, unfortunately only for this one scanner.
--
Felix E. Klee
