On Sun, 28 Nov 2004 21:04:48 -0500 (EST) fedora-list-request@redhat.com wrote:
Am So, den 28.11.2004 schrieb Nathan Low um 23:59:
I entered xsane and pressed enter then I clicked the agreement for accept. It didn't detect my scanner.
My crystal ball has actually a blind point where your scanner hardware should appear.
Surely, you jest! ;-)
That brings up a question about devices, though.
My scanner is a Umax 1200S SCSI machine that appears at /dev/sg0. This device comes equipped with permissions set to (I believe) 644 following a boot. This means that I must either don my root cape or change the permissions to 666 to use xsane. I would really like to know the *proper* way to set the permissions for that device. I stuck a line in /etc/rc.d/rc.local that reads "chmod 666 /dev/sg* &" but I would bet there's a correct way to do it.
I don't know that it may be proper but you can change the permissions in: /etc/udev/permissions.d/50-udev.permissions Look for sg in scsi area.
Richard E Miles wrote:
I don't know that it may be proper but you can change the permissions in: /etc/udev/permissions.d/50-udev.permissions Look for sg in scsi area.
I understand from http://fedora.redhat.com/docs/udev/ and rpm -qf /etc/udev/permissions.d/50-udev.permissions that this file belongs to an RPM, which is liable to get upgraded, and you'll be responsible for merging your changes and Fedora's.
# New permissions should be placed in a file, which ends in .permissions # in /etc/udev/permissions.d/. Please do not use 50-udev.permissions.
man udev says that files are read "in lexical order", which should mean that anything beginning 00 to 49 will be read before 50-udev.permissions and presumably over-ride it.
James (wading through a backlog of ~2000 list e-mails...)