3,789
edits
Changes
From Amahi Wiki
m
Look for the one that looks like That should be it's for your scanner, and write down the two numbers next to ID (in this case, if the mouse was actually a scanner, 046d and c00e). The left number is the vendor ID, and the right is the product ID. Another option is to look here: http://www.linux-usb.org/usb.ids for your manufacturer and product.
Go An alternate idea: a shell script at install, to /lib/udevset up a rule for you. Edit the 50_udev_default.rules file. You're looking for a line like this:
SUBSYSTEM=="usb if [ $UID -ne 0 ]; then echo "Please, ENV{DEVTYPE}=="usb_devicetype root's password...", NAME= su -c "bus/usb/$env{BUSNUM}/0 $env{DEVNUM}", MODE="0644@" (might be mode 0664 instead) exit fi
This says "when groupadd -r scanner usermod -a device is plugged into the USB bus, add -G scanner apache usermod -a device under /dev/bus/usb/<BUS NUMBER>called <DEVICE NUMBER>with permissions owner (-G scanner root) RW, and everyone else read only".
Add a line above that one that says: lsusb
BUS echo "Please enter the vendor ID of your scanner (number to the left of the colon):" read vend_ID echo "Please enter the product ID of your scanner (number to the right of the colon):" read product_ID echo "SUBSYSTEM==\"usb\", ATTRSATTR{idVendor}==\"<left number from lsusb>"$vend_ID"\", ATTRSATTR{idProduct}==\"<right number from lsusb>"$product_ID'", ACTION="add", NAME="bus/usb/$env{BUSNUM}/$env\{DEVNUM\}", MODEGROUP="0664scanner", GROUPOPTIONS+="last_rule"' > /etc/udev/rules.d/22_scanner.rules echo "Rules created! Please unplug and replug your scannerto finish."
This tells the system "If this SPECIFIC USB device is plugged in, make it mode 664 instead of 644, and make it part of the scanner group.
'''NOTE:''' The Fedora udev rules look a little different. You should be able to copy Basically, this makes sure the line that looks similar to script is running as root (and becomes root if not), lists the BUS="usb" line, paste itcurrently attached USB devices, and add asks for the ATTRS vendor and GROUP parts, and check the MODE to make sure it's 0664product IDs. It then pastes those into a rule that will work.
Reverted edits by Acecydoxose (Talk) to last revision by Khelmar
[[Category:Apps]]
This page is about making Amahi run as a Scanner Server.
''Your scanner must be supported by SANE for this to work.'' You can check compatibility here:
http://www.sane-project.org/sane-mfgs.html
Due to the variety of scanners available in the market (standalone, as part of a printer or fax or multifunction systems), some may experience trouble with permissions.
== Preventing permissions issues ==
You MUST have your scanner plugged in to the server before installing the app!
After installing the app, there will be a file called install_pt2.sh in the app directory (by default, /var/hda/web-apps/scanner).
To run it, use the following commands after plugging in your scanner:
su -
(enter root password)
cd /var/hda/web-apps/scanner
./install_pt2.sh
Afterward, you can delete install_pt2.sh.
The basic steps the script takes are below. If the script doesn't detect your server, or it detects the wrong one, you may need to take the steps below.
== Older instructions ==
We want to make the scanner RW for a scanner group, that Apache is a member of and has access to. To do this, start by making a new group:<BR>
su -<br> groupadd -r scanner<BR><BR>
Add apache and root to the new group:<br>
usermod -a -G scanner apache<br> usermod -a -G scanner root<br><br>
Next, we need to tell the system to set the scanner permissions so it uses the new group.
With the scanner plugged in, run the lsusb command. You'll get several lines like this:
Bus 001 002 Device 002003: ID 03f0: 5d11 Hewlett-Packard Photosmart C5200 series Look for the one that looks like it's for your scanner or printer (if the scanner is built in, as is the case above for the all-in-one printer+scanner from HP), and write down the two numbers next to ID (in this case 03f0 and 5d11). The left number is the vendor ID, and the right is the product ID 046d. Another option is to look here: http:c00e Logitech//www.linux-usb.org/usb.ids for your manufacturer and product. AS ROOT, Inccreate a file called 15-scanner. Optical Mouserules in the /etc/udev/rules.d/ directory that contains exactly one line: SUBSYSTEM=="usb", ATTR{idVendor}=="<left number from lsusb>", ATTR{idProduct}=="<right number from lsusb>", ACTION=="add",NAME="bus/usb/$env{BUSNUM}/$env{DEVNUM}", GROUP="scanner",OPTIONS+="last_rule" This tells the system "If this SPECIFIC USB device is plugged in, make it part of the scanner group with the default permissions (RW by owner and group), and stop processing rules. Save the file, then: * restart the httpd service to pick up the group permissions, via Apps -> Servers or by hand as root with: service httpd restart* unplug and replug your scanner to pick up the settings
