Changeset 2096355


Ignore:
Timestamp:
05/16/2005 02:42:00 PM (19 years ago)
Author:
Manuel Canales Esparcia <manuel@…>
Branches:
10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
Children:
c3c6502c
Parents:
b29ed97c
Message:

Tagged sane.xml

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@4301 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:
1 edited

Legend:

Unmodified
Added
Removed

  • pst/scanning/sane.xml

    rb29ed97c r2096355  
     1<?xml version="1.0" encoding="ISO-8859-1"?>
    12<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
    23   "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
    … …  
    2122
    2223<sect1 id="sane" xreflabel="SANE-&sane-version;">
    23 <sect1info>
    24 <othername>$LastChangedBy$</othername>
    25 <date>$Date$</date>
    26 </sect1info>
    27 <?dbhtml filename="sane.html"?>
    28 <title>SANE-&sane-version;</title>
    29 <indexterm zone="sane">
    30 <primary sortas="a-SANE">SANE</primary></indexterm>
    31 
    32 <sect2>
    33 <title>Introduction to
    34 <application><acronym>SANE</acronym></application></title>
    35 
    36 <para><application><acronym>SANE</acronym></application> is short for Scanner
    37 Access Now Easy. Scanner access, however, is far from easy, since every vendor
    38 has their own protocols. The only known protocol that should bring some unity
    39 into this chaos is the TWAIN interface, but this is too imprecise to allow a
    40 stable scanning framework. Therefore, <acronym>SANE</acronym> comes with its
    41 own protocol, and the vendor drivers can't be used.</para>
    42 
    43 <para><acronym>SANE</acronym> is split into back ends and front ends. The back
    44 ends are drivers for the supported scanners and cameras. The front ends are
    45 user interfaces to access the backends.</para>
    46 
    47 <sect3><title>Back ends package information</title>
    48 <itemizedlist spacing='compact'>
    49 <listitem><para>Download (HTTP): <ulink
    50 url="&sane-be-download-http;"/></para></listitem>
    51 <listitem><para>Download (FTP): <ulink
    52 url="&sane-be-download-ftp;"/></para></listitem>
    53 <listitem><para>Download MD5 sum: &sane-be-md5sum;</para></listitem>
    54 <listitem><para>Download size: &sane-be-size;</para></listitem>
    55 <listitem><para>Estimated disk space required:
    56 &sane-be-buildsize;</para></listitem>
    57 <listitem><para>Estimated build time:
    58 &sane-be-time;</para></listitem></itemizedlist>
    59 </sect3>
    60 
    61 <sect3><title>Front ends package information</title>
    62 <itemizedlist spacing='compact'>
    63 <listitem><para>Download (HTTP): <ulink
    64 url="&sane-fe-download-http;"/></para></listitem>
    65 <listitem><para>Download (FTP): <ulink
    66 url="&sane-fe-download-ftp;"/></para></listitem>
    67 <listitem><para>Downlaod MD5 sum: &sane-fe-md5sum;</para></listitem>
    68 <listitem><para>Download size: &sane-fe-size;</para></listitem>
    69 <listitem><para>Estimated disk space required:
    70 &sane-fe-buildsize;</para></listitem>
    71 <listitem><para>Estimated build time:
    72 &sane-fe-time;</para></listitem></itemizedlist>
    73 </sect3>
    74 
    75 <sect3><title><application><acronym>SANE</acronym></application>
    76 dependencies</title>
    77 <sect4><title>Optional (back ends)</title>
    78 <para><xref linkend="libjpeg"/>,
    79 <xref linkend="libusb"/>,
    80 <ulink url="http://cyberelk.net/tim/libieee1284/">libieee1284</ulink>,
    81 <ulink url="http://www.gphoto.org/">gPhoto2</ulink>
    82 (requires <ulink url="http://www.gphoto.org/">libgphoto2</ulink>) and
    83 <xref linkend="tex"/></para>
    84 </sect4>
    85 
    86 <sect4><title>Optional (front ends)</title>
    87 <para>X (<xref linkend="xfree86"/> or <xref linkend="xorg"/>),
    88 <xref linkend="gtk2"/> and
    89 <xref linkend="gimp"/></para>
    90 </sect4>
    91 </sect3>
    92 
    93 </sect2>
    94 
    95 <sect2>
    96 <title>Installation of
    97 <application><acronym>SANE</acronym></application></title>
    98 
    99 <sect3 id="sane-kernel"><title>Preparing your system for scanner access</title>
    100 <indexterm zone="sane sane-kernel">
    101 <primary sortas="d-Scanning-devices">Scanning devices</primary></indexterm>
    102 
    103 <para>To access your scanner, you will probably need the related kernel
    104 drivers or additional support packages (<xref linkend="libusb"/>).
    105 A <acronym>SCSI</acronym> scanner will need <acronym>SCSI</acronym>
    106 drivers, a parallel port scanner needs parallel port support (you should use
    107 enhanced <acronym>EPP</acronym> modes) and a <acronym>USB</acronym> scanner
    108 will need the <application>libusb</application> package and a
    109 <acronym>SCSI</acronym> system for emulation. Be sure that you have got the
    110 necessary drivers configured to access the devices.</para>
    111 </sect3>
    112 
    113 <sect3><title>Installation of
    114 <application><acronym>SANE</acronym></application> back ends</title>
    115 
    116 <para>Install <application><acronym>SANE</acronym></application>-backends by
    117 running the following commands:</para>
    118 
    119 <screen><userinput><command>./configure --prefix=/usr --sysconfdir=/etc &amp;&amp;
    120 make</command></userinput></screen>
    121 
    122 <para>Now, as the root user:</para>
    123 
    124 <screen><userinput role='root'><command>make install</command></userinput></screen>
    125 </sect3>
    126 
    127 <sect3><title>Installation of
    128 <application><acronym>SANE</acronym></application> front ends</title>
    129 
    130 <para>The <application><acronym>SANE</acronym></application>-frontends package
    131 includes the graphical frontends <command>xscanimage</command> and
    132 <command>xcam</command>, and a command-line frontend
    133 <command>scanadf</command>. You don't need this package if you intend to use
    134 one of the more advanced graphical frontends like <xref linkend="xsane"/>. For
    135 a list of frontend packages, see
    136 <ulink url="http://www.sane-project.org/sane-frontends.html"/>.</para>
    137 
    138 <para>To install <application><acronym>SANE</acronym></application>-frontends,
    139 use the following commands:</para>
    140 
    141 <screen><userinput><command>./configure --prefix=/usr &amp;&amp;
    142 make</command></userinput></screen>
    143 
    144 <para>Now, as the root user:</para>
    145 
    146 <screen><userinput role='root'><command>make install</command></userinput></screen>
    147 
    148 <para>If <application>GIMP</application> was linked into the build and you
    149 wish <application>GIMP</application> to use <command>xscanimage</command> as
    150 a scanning plugin, issue the following command as the root user:</para>
    151 
    152 <screen><userinput role='root'><command>ln -s /usr/bin/xscanimage /usr/lib/gimp/2.0/plug-ins</command></userinput></screen>
    153 </sect3>
    154 
    155 </sect2>
    156 
    157 <sect2>
    158 <title>Command explanations</title>
    159 
    160 <para><parameter>--sysconfdir=/etc</parameter>: This switch installs the
    161 configuration files in <filename class="directory">/etc/sane.d</filename>
    162 instead of <filename class="directory">/usr/etc/sane.d</filename>.</para>
    163 
    164 </sect2>
    165 
    166 <sect2>
    167 <title>Configuring <application><acronym>SANE</acronym></application></title>
    168 
    169 <sect3 id="sane-config"><title>Config files</title>
    170 <para><filename>/etc/sane.d/*.conf</filename></para>
    171 <indexterm zone="sane sane-config">
    172 <primary sortas="e-etc-sane.d-conf">/etc/sane.d/*.conf</primary></indexterm>
    173 </sect3>
    174 
    175 <sect3><title>Configuration information</title>
    176 <sect4><title>Backend configuration</title>
    177 <para>The backend configuration files are located in
    178 <filename class='directory'>/etc/sane.d</filename>. Information for configuring
    179 the various backends can be found by using the man(5) page for the desired
    180 backend. Run <command>man sane-<replaceable>[backend]</replaceable></command>,
    181 substituting the desired backend.</para>
    182 </sect4>
    183 
    184 <sect4><title>General information</title>
    185 <para>For general information about configuring and using
    186 <application><acronym>SANE</acronym></application>, see
    187 <command>man sane</command>. Linux-2.6.x brings some special issues into the
    188 picture. See <ulink url="http://www.sane-project.org/README.linux"/> for
    189 information about using <application><acronym>SANE</acronym></application>
    190 with the Linux-2.6.x kernel. For information about <acronym>USB</acronym>
    191 scanning devices, run <command>man sane-usb</command>. For information about
    192 <acronym>SCSI</acronym> devices, run <command>man sane-scsi</command>.</para>
    193 </sect4>
    194 
    195 <sect4><title>Configuration and setup of the <command>saned</command>
    196 daemon</title>
    197 <para>The <command>saned</command> daemon is not meant to be used for
    198 untrusted clients. You should provide <xref linkend="tcpwrappers"/> and/or
    199 <xref linkend="fw-firewall"/> protection to insure only trusted clients access
    200 the daemon. Due to the complex security requirements to insure only trusted
    201 clients access the daemon, <acronym>BLFS</acronym> does not provide
    202 instructions to configure the <command>saned</command> daemon. If you desire
    203 to make the daemon available, ensure you provide adequate security, configure
    204 your <filename>[x]inetd.conf</filename> file and send a
    205 <userinput>SIGHUP</userinput> to the [x]inetd daemon. Some good information for
    206 setting up and securing the <command>saned</command> daemon can be found at
    207 <ulink url="http://penguin-breeder.org/sane/saned/"/>.</para>
    208 </sect4>
    209 </sect3>
    210 
    211 </sect2>
    212 
    213 <sect2>
    214 <title>Contents</title>
    215 
    216 <bridgehead renderas="sect4">Back Ends:</bridgehead>
    217 <segmentedlist>
    218 <segtitle>Installed Programs</segtitle>
    219 <segtitle>Installed Libraries</segtitle>
    220 <segtitle>Installed Directories</segtitle>
    221 
    222 <seglistitem>
    223 <seg>gamma4scanimage, sane-config, saned, sane-find-scanner and scanimage</seg>
    224 <seg>libsane.so and numerous scanner backend modules</seg>
    225 <seg>/etc/sane.d, /usr/include/sane, /usr/lib/sane, /usr/share/sane and
    226 /usr/share/doc/sane-&sane-version;</seg>
    227 </seglistitem>
    228 </segmentedlist>
    229 
    230 <bridgehead renderas="sect4">Front Ends:</bridgehead>
    231 <segmentedlist>
    232 <segtitle>Installed Programs</segtitle>
    233 <segtitle>Installed Library</segtitle>
    234 <segtitle>Installed Directory</segtitle>
    235 
    236 <seglistitem>
    237 <seg>scanadf, xcam and xscanimage</seg>
    238 <seg><application>GIMP</application> plugin imbedded in
    239 <command>xscanimage</command></seg>
    240 <seg>/usr/share/sane</seg>
    241 </seglistitem>
    242 </segmentedlist>
    243 
    244 <variablelist>
    245 <bridgehead renderas="sect3">Short Descriptions</bridgehead>
    246 <?dbfo list-presentation="list"?>
    247 
    248 <varlistentry id="gamma4scanimage">
    249 <term><command>gamma4scanimage</command></term>
    250 <listitem><para>creates a gamma table in the format expected by
    251 <command>scanimage</command>.</para>
    252 <indexterm zone="sane gamma4scanimage">
    253 <primary sortas="b-gamma4scanimage">gamma4scanimage</primary>
    254 </indexterm></listitem>
    255 </varlistentry>
    256 
    257 <varlistentry id="sane-config-prog">
    258 <term><command>sane-config</command></term>
    259 <listitem><para>is a tool used to determine the compiler and linker flags that
    260 should be used to compile and link
    261 <application><acronym>SANE</acronym></application>.</para>
    262 <indexterm zone="sane sane-config-prog">
    263 <primary sortas="b-sane-config">sane-config</primary>
    264 </indexterm></listitem>
    265 </varlistentry>
    266 
    267 <varlistentry id="saned">
    268 <term><command>saned</command></term>
    269 <listitem><para>is the <application><acronym>SANE</acronym></application>
    270 daemon that allows remote clients to access image acquisition devices
    271 available on the local host.</para>
    272 <indexterm zone="sane saned">
    273 <primary sortas="b-saned">saned</primary>
    274 </indexterm></listitem>
    275 </varlistentry>
    276 
    277 <varlistentry id="sane-find-scanner">
    278 <term><command>sane-find-scanner</command></term>
    279 <listitem><para>is a command-line tool to find <acronym>SCSI</acronym> and
    280 <acronym>USB</acronym> scanners and determine their device files. Its primary
    281 aim is to make sure that scanners can be detected by
    282 <application><acronym>SANE</acronym></application> backends.</para>
    283 <indexterm zone="sane sane-find-scanner">
    284 <primary sortas="b-sane-find-scanner">sane-find-scanner</primary>
    285 </indexterm></listitem>
    286 </varlistentry>
    287 
    288 <varlistentry id="scanadf">
    289 <term><command>scanadf</command></term>
    290 <listitem><para>is a command-line interface to control image acquisition
    291 devices which are equipped with an automatic document feeder
    292 (<acronym>ADF</acronym>).</para>
    293 <indexterm zone="sane scanadf">
    294 <primary sortas="b-scanadf">scanadf</primary>
    295 </indexterm></listitem>
    296 </varlistentry>
    297 
    298 <varlistentry id="scanimage">
    299 <term><command>scanimage</command></term>
    300 <listitem><para>is a command line interface for scanning from image
    301 acquisition devices such as flatbed scanners or cameras. It is also used to
    302 list the available backend devices.</para>
    303 <indexterm zone="sane scanimage">
    304 <primary sortas="b-scanimage">scanimage</primary>
    305 </indexterm></listitem>
    306 </varlistentry>
    307 
    308 <varlistentry id="xcam">
    309 <term><command>xcam</command></term>
    310 <listitem><para>is a graphical camera front end for
    311 <application><acronym>SANE</acronym></application>.</para>
    312 <indexterm zone="sane xcam">
    313 <primary sortas="b-xcam">xcam</primary>
    314 </indexterm></listitem>
    315 </varlistentry>
    316 
    317 <varlistentry id="xscanimage">
    318 <term><command>xscanimage</command></term>
    319 <listitem><para>is a graphical user interface for scanning.</para>
    320 <indexterm zone="sane xscanimage">
    321 <primary sortas="b-xscanimage">xscanimage</primary>
    322 </indexterm></listitem>
    323 </varlistentry>
    324 
    325 <varlistentry id="libsane">
    326 <term><filename class='libraryfile'>libsane.so</filename></term>
    327 <listitem><para>is the application programming interface that is used to
    328 communicate between frontends and backends.</para>
    329 <indexterm zone="sane libsane">
    330 <primary sortas="c-libsane">libsane.so</primary>
    331 </indexterm></listitem>
    332 </varlistentry>
    333 
    334 <varlistentry id="libsane-module">
    335 <term><filename class='libraryfile'>libsane-*.so</filename></term>
    336 <listitem><para>modules are backend scanning library plugins used to interface
    337 with scanning devices. See
    338 <ulink url="http://www.sane-project.org/sane-supported-devices.html"/>
    339 for a list of supported backends.</para>
    340 <indexterm zone="sane libsane-module">
    341 <primary sortas="c-libsane-module">libsane-*.so</primary>
    342 </indexterm></listitem>
    343 </varlistentry>
    344 </variablelist>
    345 
    346 </sect2>
     24  <?dbhtml filename="sane.html"?>
     25
     26  <sect1info>
     27    <othername>$LastChangedBy$</othername>
     28    <date>$Date$</date>
     29  </sect1info>
     30
     31  <title>SANE-&sane-version;</title>
     32
     33  <indexterm zone="sane">
     34    <primary sortas="a-SANE">SANE</primary>
     35  </indexterm>
     36
     37  <sect2 role="package">
     38    <title>Introduction to SANE</title>
     39
     40    <para><application>SANE</application> is short for Scanner Access Now Easy.
     41    Scanner access, however, is far from easy, since every vendor has their own
     42    protocols. The only known protocol that should bring some unity into this
     43    chaos is the TWAIN interface, but this is too imprecise to allow a stable
     44    scanning framework. Therefore, SANE comes with its own protocol, and the
     45    vendor drivers can't be used.</para>
     46
     47    <para>SANE is split into back ends and front ends. The back ends are drivers
     48    for the supported scanners and cameras. The front ends are user interfaces
     49    to access the backends.</para>
     50
     51    <bridgehead renderas="sect3">Back Ends Package Information</bridgehead>
     52    <itemizedlist spacing='compact'>
     53      <listitem>
     54        <para>Download (HTTP): <ulink url="&sane-be-download-http;"/></para>
     55      </listitem>
     56      <listitem>
     57        <para>Download (FTP): <ulink url="&sane-be-download-ftp;"/></para>
     58      </listitem>
     59      <listitem>
     60        <para>Download MD5 sum: &sane-be-md5sum;</para>
     61      </listitem>
     62      <listitem>
     63        <para>Download size: &sane-be-size;</para>
     64      </listitem>
     65      <listitem>
     66        <para>Estimated disk space required: &sane-be-buildsize;</para>
     67      </listitem>
     68      <listitem>
     69        <para>Estimated build time: &sane-be-time;</para>
     70      </listitem>
     71    </itemizedlist>
     72
     73    <bridgehead renderas="sect3">Front Ends Package Information</bridgehead>
     74    <itemizedlist spacing='compact'>
     75      <listitem>
     76        <para>Download (HTTP): <ulink url="&sane-fe-download-http;"/></para>
     77      </listitem>
     78      <listitem>
     79        <para>Download (FTP): <ulink url="&sane-fe-download-ftp;"/></para>
     80      </listitem>
     81      <listitem>
     82        <para>Downlaod MD5 sum: &sane-fe-md5sum;</para>
     83      </listitem>
     84      <listitem>
     85        <para>Download size: &sane-fe-size;</para>
     86      </listitem>
     87      <listitem>
     88        <para>Estimated disk space required: &sane-fe-buildsize;</para>
     89      </listitem>
     90      <listitem>
     91        <para>Estimated build time: &sane-fe-time;</para>
     92      </listitem>
     93    </itemizedlist>
     94
     95    <bridgehead renderas="sect3">SANE Dependencies</bridgehead>
     96
     97    <bridgehead renderas="sect4">Optional (Back Ends)</bridgehead>
     98    <para><xref linkend="libjpeg"/>,
     99    <xref linkend="libusb"/>,
     100    <ulink url="http://cyberelk.net/tim/libieee1284/">libieee1284</ulink>,
     101    <ulink url="http://www.gphoto.org/">gPhoto2</ulink>
     102    (requires <ulink url="http://www.gphoto.org/">libgphoto2</ulink>) and
     103    <xref linkend="tex"/></para>
     104
     105    <bridgehead renderas="sect4">Optional (Front Ends)</bridgehead>
     106    <para>X (<xref linkend="xfree86"/> or <xref linkend="xorg"/>),
     107    <xref linkend="gtk2"/> and
     108    <xref linkend="gimp"/></para>
     109
     110  </sect2>
     111
     112  <sect2 role="kernel" id='sane-kernel'>
     113    <title>Kernel Configuration</title>
     114
     115    <indexterm zone="sane sane-kernel">
     116      <primary sortas="d-Scanning-devices">Scanning devices</primary>
     117    </indexterm>
     118
     119    <para>To access your scanner, you will probably need the related kernel
     120    drivers or additional support packages (<xref linkend="libusb"/>).
     121    A SCSI scanner will need SCSI drivers, a parallel port scanner needs
     122    parallel port support (you should use enhanced EPP modes) and a USB
     123    scanner will need the <application>libusb</application> package and a
     124    SCSI system for emulation. Be sure that you have got the necessary
     125    drivers configured to access the devices.</para>
     126
     127  </sect2>
     128
     129  <sect2 role="installation">
     130    <title>Installation of SANE</title>
     131
     132    <sect3>
     133      <title>Installation of SANE Back Ends</title>
     134
     135      <para>Install <application>SANE</application>-backends by
     136      running the following commands:</para>
     137
     138<screen><userinput>./configure --prefix=/usr --sysconfdir=/etc &amp;&amp;
     139make</userinput></screen>
     140
     141      <para>Now, as the <systemitem class="username">root</systemitem> user:</para>
     142
     143<screen role="root"><userinput>make install</userinput></screen>
     144
     145    </sect3>
     146
     147    <sect3>
     148      <title>Installation of SANE Front Ends</title>
     149
     150      <para>The <application>SANE</application>-frontends package
     151      includes the graphical frontends <command>xscanimage</command> and
     152      <command>xcam</command>, and a command-line frontend
     153      <command>scanadf</command>. You don't need this package if you intend
     154      to use one of the more advanced graphical frontends like
     155      <xref linkend="xsane"/>. For a list of frontend packages, see
     156      <ulink url="http://www.sane-project.org/sane-frontends.html"/>.</para>
     157
     158      <para>To install <application>SANE</application>-frontends,
     159      use the following commands:</para>
     160
     161<screen><userinput>./configure --prefix=/usr &amp;&amp;
     162make</userinput></screen>
     163
     164      <para>Now, as the <systemitem class="username">root</systemitem> user:</para>
     165
     166<screen role="root"><userinput>make install</userinput></screen>
     167
     168      <para>If <application>GIMP</application> was linked into the build
     169      and you wish <application>GIMP</application> to use
     170      <command>xscanimage</command> as a scanning plugin, issue the following
     171      command as the <systemitem class="username">root</systemitem> user:</para>
     172
     173<screen role="root"><userinput>ln -v -s /usr/bin/xscanimage /usr/lib/gimp/2.0/plug-ins</userinput></screen>
     174
     175    </sect3>
     176
     177  </sect2>
     178
     179  <sect2 role="commands">
     180    <title>Command Explanations</title>
     181
     182    <para><parameter>--sysconfdir=/etc</parameter>: This switch installs the
     183    configuration files in <filename class="directory">/etc/sane.d</filename>
     184    instead of <filename class="directory">/usr/etc/sane.d</filename>.</para>
     185
     186  </sect2>
     187
     188  <sect2 role="configuration">
     189    <title>Configuring SANE</title>
     190
     191    <sect3 id="sane-config">
     192      <title>Config Files</title>
     193
     194      <para><filename>/etc/sane.d/*.conf</filename></para>
     195
     196      <indexterm zone="sane sane-config">
     197        <primary sortas="e-etc-sane.d-conf">/etc/sane.d/*.conf</primary>
     198      </indexterm>
     199
     200    </sect3>
     201
     202    <sect3>
     203      <title>Configuration Information</title>
     204
     205      <sect4>
     206        <title>Backend Configuration</title>
     207
     208        <para>The backend configuration files are located in
     209        <filename class='directory'>/etc/sane.d</filename>. Information
     210        for configuring the various backends can be found by using the man(5)
     211        page for the desired backend. Run
     212        <command>man sane-<replaceable>[backend]</replaceable></command>,
     213        substituting the desired backend.</para>
     214
     215      </sect4>
     216
     217      <sect4>
     218        <title>General Information</title>
     219
     220        <para>For general information about configuring and using
     221        <application>SANE</application>, see <command>man sane</command>.
     222        Linux-2.6.x brings some special issues into the picture. See
     223        <ulink url="http://www.sane-project.org/README.linux"/> for
     224        information about using <application>SANE</application> with the
     225        Linux-2.6.x kernel. For information about USB scanning devices,
     226        run <command>man sane-usb</command>. For information about SCSI
     227        devices, run <command>man sane-scsi</command>.</para>
     228
     229      </sect4>
     230
     231      <sect4>
     232        <title>Configuration and setup of the 'saned' daemon</title>
     233
     234        <para>The <command>saned</command> daemon is not meant to be used for
     235        untrusted clients. You should provide <xref linkend="tcpwrappers"/>
     236        and/or <xref linkend="fw-firewall"/> protection to insure only trusted
     237        clients access the daemon. Due to the complex security requirements to
     238        insure only trusted clients access the daemon, BLFS does not provide
     239        instructions to configure the <command>saned</command> daemon. If you
     240        desire to make the daemon available, ensure you provide adequate
     241        security, configure your <filename>[x]inetd.conf</filename> file and
     242        send a <userinput>SIGHUP</userinput> to the [x]inetd daemon. Some good
     243        information for setting up and securing the <command>saned</command>
     244        daemon can be found at
     245        <ulink url="http://penguin-breeder.org/sane/saned/"/>.</para>
     246
     247      </sect4>
     248
     249    </sect3>
     250
     251  </sect2>
     252
     253  <sect2 role="content">
     254    <title>Contents</title>
     255
     256    <bridgehead renderas="sect4">Back Ends:</bridgehead>
     257    <segmentedlist>
     258      <segtitle>Installed Programs</segtitle>
     259      <segtitle>Installed Libraries</segtitle>
     260      <segtitle>Installed Directories</segtitle>
     261
     262      <seglistitem>
     263        <seg>gamma4scanimage, sane-config, saned, sane-find-scanner,
     264        and scanimage</seg>
     265        <seg>libsane.so and numerous scanner backend modules</seg>
     266        <seg>/etc/sane.d, /usr/include/sane, /usr/lib/sane, /usr/share/sane, and
     267        /usr/share/doc/sane-&sane-version;</seg>
     268      </seglistitem>
     269    </segmentedlist>
     270
     271    <bridgehead renderas="sect4">Front Ends:</bridgehead>
     272    <segmentedlist>
     273      <segtitle>Installed Programs</segtitle>
     274      <segtitle>Installed Library</segtitle>
     275      <segtitle>Installed Directory</segtitle>
     276
     277      <seglistitem>
     278        <seg>scanadf, xcam, and xscanimage</seg>
     279        <seg><application>GIMP</application> plugin imbedded in
     280        <command>xscanimage</command></seg>
     281        <seg>/usr/share/sane</seg>
     282      </seglistitem>
     283    </segmentedlist>
     284
     285    <variablelist>
     286      <bridgehead renderas="sect3">Short Descriptions</bridgehead>
     287      <?dbfo list-presentation="list"?>
     288      <?dbhtml list-presentation="table"?>
     289
     290      <varlistentry id="gamma4scanimage">
     291        <term><command>gamma4scanimage</command></term>
     292        <listitem>
     293          <para>creates a gamma table in the format expected by
     294          <command>scanimage</command>.</para>
     295          <indexterm zone="sane gamma4scanimage">
     296            <primary sortas="b-gamma4scanimage">gamma4scanimage</primary>
     297          </indexterm>
     298        </listitem>
     299      </varlistentry>
     300
     301      <varlistentry id="sane-config-prog">
     302        <term><command>sane-config</command></term>
     303        <listitem>
     304          <para>is a tool used to determine the compiler and linker
     305          flags that should be used to compile and link
     306          <application>SANE</application>.</para>
     307          <indexterm zone="sane sane-config-prog">
     308            <primary sortas="b-sane-config">sane-config</primary>
     309          </indexterm>
     310        </listitem>
     311      </varlistentry>
     312
     313      <varlistentry id="saned">
     314        <term><command>saned</command></term>
     315        <listitem>
     316          <para>is the <application>SANE</application> daemon that
     317          allows remote clients to access image acquisition devices
     318          available on the local host.</para>
     319          <indexterm zone="sane saned">
     320            <primary sortas="b-saned">saned</primary>
     321          </indexterm>
     322        </listitem>
     323      </varlistentry>
     324
     325      <varlistentry id="sane-find-scanner">
     326        <term><command>sane-find-scanner</command></term>
     327        <listitem>
     328          <para>is a command-line tool to find SCSI and
     329          USB scanners and determine their device files. Its primary
     330          aim is to make sure that scanners can be detected by
     331          <application>SANE</application> backends.</para>
     332          <indexterm zone="sane sane-find-scanner">
     333            <primary sortas="b-sane-find-scanner">sane-find-scanner</primary>
     334          </indexterm>
     335        </listitem>
     336      </varlistentry>
     337
     338      <varlistentry id="scanadf">
     339        <term><command>scanadf</command></term>
     340        <listitem>
     341          <para>is a command-line interface to control image acquisition
     342          devices which are equipped with an automatic document feeder
     343          (ADF).</para>
     344          <indexterm zone="sane scanadf">
     345            <primary sortas="b-scanadf">scanadf</primary>
     346          </indexterm>
     347        </listitem>
     348      </varlistentry>
     349
     350      <varlistentry id="scanimage">
     351        <term><command>scanimage</command></term>
     352        <listitem>
     353          <para>is a command line interface for scanning from image acquisition
     354          devices such as flatbed scanners or cameras. It is also used to list
     355          the available backend devices.</para>
     356          <indexterm zone="sane scanimage">
     357            <primary sortas="b-scanimage">scanimage</primary>
     358          </indexterm>
     359        </listitem>
     360      </varlistentry>
     361
     362      <varlistentry id="xcam">
     363        <term><command>xcam</command></term>
     364        <listitem>
     365          <para>is a graphical camera front end for
     366          <application>SANE</application>.</para>
     367          <indexterm zone="sane xcam">
     368            <primary sortas="b-xcam">xcam</primary>
     369          </indexterm>
     370        </listitem>
     371      </varlistentry>
     372
     373      <varlistentry id="xscanimage">
     374        <term><command>xscanimage</command></term>
     375        <listitem>
     376          <para>is a graphical user interface for scanning.</para>
     377          <indexterm zone="sane xscanimage">
     378            <primary sortas="b-xscanimage">xscanimage</primary>
     379          </indexterm>
     380        </listitem>
     381      </varlistentry>
     382
     383      <varlistentry id="libsane">
     384        <term><filename class='libraryfile'>libsane.so</filename></term>
     385        <listitem>
     386          <para>is the application programming interface that is used to
     387          communicate between frontends and backends.</para>
     388          <indexterm zone="sane libsane">
     389            <primary sortas="c-libsane">libsane.so</primary>
     390          </indexterm>
     391        </listitem>
     392      </varlistentry>
     393
     394      <varlistentry id="libsane-module">
     395        <term><filename class='libraryfile'>libsane-*.so</filename></term>
     396        <listitem>
     397          <para>modules are backend scanning library plugins used to interface
     398          with scanning devices. See
     399          <ulink url="http://www.sane-project.org/sane-supported-devices.html"/>
     400          for a list of supported backends.</para>
     401          <indexterm zone="sane libsane-module">
     402            <primary sortas="c-libsane-module">libsane-*.so</primary>
     403          </indexterm>
     404        </listitem>
     405      </varlistentry>
     406
     407    </variablelist>
     408
     409  </sect2>
    347410
    348411</sect1>
Note: See TracChangeset for help on using the changeset viewer.