%general-entities; ]> $LastChangedBy$ $Date$ SANE-&sane-version; Introduction to <application><acronym>SANE</acronym></application> SANE is short for Scanner Access Now Easy. Scanner access, however, is far from easy, since every vendor has their own protocols. The only known protocol that should bring some unity into this chaos is the TWAIN interface, but this is too imprecise to allow a stable scanning framework. Therefore, SANE comes with its own protocol, and the vendor drivers can't be used. SANE is split into back ends and front ends. The back ends are drivers for the supported scanners and cameras. The front ends are user interfaces to access the backends. Back ends package information Download (HTTP): Download (FTP): Download MD5 sum: &sane-be-md5sum; Download size: &sane-be-size; Estimated disk space required: &sane-be-buildsize; Estimated build time: &sane-be-time; Front ends package information Download (HTTP): Download (FTP): Downlaod MD5 sum: &sane-fe-md5sum; Download size: &sane-fe-size; Estimated disk space required: &sane-fe-buildsize; Estimated build time: &sane-fe-time; <application><acronym>SANE</acronym></application> dependencies Optional (back ends) , , libieee1284, gPhoto2 (requires libgphoto2) and Optional (front ends) X ( or ), and Installation of <application><acronym>SANE</acronym></application> Preparing your system for scanner access To access your scanner, you will probably need the related kernel drivers or additional support packages (libusb). A SCSI scanner will need SCSI drivers, a parallel port scanner needs parallel port support (you should use enhanced EPP modes) and a USB scanner will need the libusb package and a SCSI system for emulation. Be sure that you have got the necessary drivers to access the devices. Installation of <application><acronym>SANE</acronym></application> back ends Install SANE-backends by running the following commands: ./configure --prefix=/usr --sysconfdir=/etc && make && make install Installation of <application><acronym>SANE</acronym></application> front ends The SANE-frontends package includes the graphical frontends xscanimage and xcam, and a command-line frontend scanadf. You don't need this package if you intend to use one of the more advanced graphical frontends like . For a list of frontend packages, see . To install SANE-frontends, use the following commands: ./configure --prefix=/usr && make && make install If GIMP was linked into the build and you wish GIMP to use xscanimage as a scanning plugin, issue the following command: ln -s /usr/bin/xscanimage /usr/lib/gimp/2.0/plug-ins Command explanations --sysconfdir=/etc: This switch installs the configuration files in /etc/sane.d instead of /usr/etc/sane.d. Configuring <application><acronym>SANE</acronym></application> Config files /etc/sane.d/*.conf Configuration information Backend configuration The backend configuration files are located in /etc/sane.d. Information for configuring the various backends can be found by using the man(5) page for the desired backend. Run man sane-[backend], substituting the desired backend. General information For general information about configuring and using SANE, see man sane. Linux-2.6.x brings some special issues into the picture. See for information about using SANE with the Linux-2.6.x kernel. For information about USB scanning devices, run man sane-usb. For information about SCSI devices, run man sane-scsi. Configuration and setup of the <command>saned</command> daemon The saned daemon is not meant to be used for untrusted clients. You should provide tcpwrapper and/or firewall protection to insure only trusted clients access the daemon. Due to the complex security requirements to insure only trusted clients access the daemon, BLFS does not provide instructions to configure the saned daemon. If you desire to make the daemon available, ensure you provide adequate security, configure your [x]inetd.conf file and send a SIGHUP to the [x]inetd daemon. Some good information for setting up and securing the saned daemon can be found at . Contents Back ends: The SANE-backends package contains gamma4scanimage, sane-config, saned, sane-find-scanner, scanimage, the libsane library and numerous scanner backend modules. See for a list of supported backends. Front ends: The SANE-frontends package contains scanadf, xcam, xscanimage and a GIMP plugin imbedded in xscanimage. Description gamma4scanimage gamma4scanimage creates a gamma table in the format expected by scanimage. sane-config sane-config is a tool used to determine the compiler and linker flags that should be used to compile and link SANE. saned saned is the SANE daemon that allows remote clients to access image acquisition devices available on the local host. sane-find-scanner sane-find-scanner is a command-line tool to find SCSI and USB scanners and determine their device files. Its primary aim is to make sure that scanners can be detected by SANE backends. scanadf scanadf is a command-line interface to control image acquisition devices which are equipped with an automatic document feeder (ADF). scanimage scanimage is a command line interface for scanning from image acquisition devices such as flatbed scanners or cameras. It is also used to list the available backend devices. xcam xcam is a graphical camera front end for SANE. xscanimage xscanimage is a graphical user interface for scanning.