3,789
edits
Changes
From Amahi Wiki
m
Look for the one that looks like it's for your scannerAS ROOT, and write down the two numbers next to ID (in this case, if the mouse was actually create a file called 15-scanner, 046d and c00e). The left number is rules in the vendor ID, and the right is the product ID. Another option is to look here: http:/etc/udev/www.linux-usbrules.orgd/usb.ids for your manufacturer and product.directory that contains exactly one line:
Go to /etc/udev/rules.d/ AS ROOT.<p>Create a file 15_scanner.rules that contains:<br> 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"<br><br>
<p>
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 046d03f0:c00e Logitech5d11 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, Incand the right is the product ID. Another option is to look here: http://www.linux-usb.org/usb.ids for your manufacturer and product. Optical Mouse
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, and 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 That should be it. An alternate idea: a shell script at install, to set up a rule for you. if [ $UID -ne 0 ]; then echo "Please, type root's password..." su -c "$0 $@" exit fi groupadd -r scanner usermod -a -G scanner apache usermod -a -G scanner root lsusb 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\", ATTR{idVendor}==\""$vend_ID"\",ATTR{idProduct}==\""$product_ID'", ACTION="add",NAME="bus/usb/$env{BUSNUM}/$env\{DEVNUM\}", GROUP="scanner",OPTIONS+="last_rule"' > /etc/udev/rules.d/22_scanner.rules echo "Rules created! Please unplug and replug your scanner to finish." Basically, this makes sure the script is running as root (and becomes root if not), lists the currently attached USB devices, and asks for the vendor and product IDs. It then pastes those into a rule that will work.
