Mailinglist Archive: opensuse (2372 mails)

[Bob Kline <bkline@xxxxxxxxxxxxx>]

M Harris wrote:
> On Friday 08 June 2007 14:35, Bob Kline wrote:
> > I've tried chmod on the /dev files, but that doesn't stick.  I'm not
> > surprised: I assume that the device files are set up on the fly, but I
> > don't know how to control the permissions.
> 	I found your answer... 
>
>         ... check section 5.3 of this FAQ:
>
>         http://www.xs4all.nl/~ljm/SANE-faq.html#46

Thanks for your reply.  I've looked at this FAQ.  It says:

[[[ start quote ]]]
scanimage -L

This will give you the name of the device. For example:

[ljm@ronsard ~]$ scanimage -L
device `umax:/dev/sgd' is a UMAX     Astra 1220S      flatbed scanner
[ljm@ronsard ~]$

The /dev/sgd is the name of the device.
[[[ end quote ]]]

In my case, the output of scanimage -L is

device `plustek:libusb:007:002' is a Canon N1240U/LiDE30 USB flatbed scanner

which doesn't give me a name of a file but is using some other syntax.  
The answer to the FAQ goes on to talk about finding the lines in the 
file /etc/security/console.perms and commenting them out.  There is no 
such file in my /etc/security directory.  In fact, I've looked at every 
file that is in that directory, and almost none of the non-empty lines 
in any of the files are uncommented to start with, and I promise that 
none of the ones which aren't commented make any reference to the 
scanner.  Then the FAQ talks about "users of the device filesystem" and 
"/etc/devfs/perms" which I assume doesn't apply to this installation of 
SuSE, as /etc/devfs doesn't exist.  The FAQ ends with "For USB scanner, 
have a look at the USB-section."

So I did.  That section starts of by talking about using chmod on files 
in /proc/bus/usb.  I don't have any files there, and that's not a 
durable solution anyway ("the permissions will be reset when the scanner 
is replugged or Linux is rebooted").  Then:

"One solution to set permissions on-the-fly are the Linux hot-plug tools 
that should come with any current distribution. SANE itsself comes with 
a hotplug script and related documentation in the tools/hotplug/ 
directory. Please refer to the README in that directory for the details. 
You might also wish to browse through the documentation for the Plustek; 
it has quite a nice section on how to set-up your USB access.

/usr/share/doc/sane-backends-*/plustek/Plustek-USB.txt"

I don't see any evidence that the statement about SANE including hotplug 
tools is actually true:

$ rpm -qa | grep -i sane
xsane-0.991-32
sane-frontends-1.0.14-44
sane-1.0.18-34
$ rpm -ql sane | grep -i hotplug
$ rpm -ql sane-fontends | grep -i hotplug
$ rpm -ql xsane | grep -i hotplug
$  man hotplug
No manual entry for hotplug

I'm **way** out of my systems administration here. :-(

--
Bob Kline
http://www.rksystems.com
mailto:bkline@xxxxxxxxxxxxx

--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx