mirror
/
sane-project-website
kopia lustrzana https://gitlab.com/sane-project/website
1
0
Forkuj 0
Kod Zgłoszenia Projekty Wydania Wiki Aktywność

update old manpages, change iscan link

merge-requests/1/head
m. allan noah 2010-02-10 10:23:52 -05:00
rodzic ccddbca395
commit 76b72727a3
4 zmienionych plików z 288 dodań i 456 usunięć
Pokaż statystyki Ściągnij plik aktualizacji Ściągnij plik porównania Expand all files Collapse all files

153
man/sane.7.html
Wyświetl plik

@ -47,9 +47,9 @@
(including the <B>SANE</B> standard), networking support, and the command line
frontend '<B>scanimage</B>'. The frontends '<B>xscanimage</B>', '<B>xcam</B>', and
'<B>scanadf</B>' are included in the package '<B>sane-frontends</B>'. Both packages
can be downloaded from the <B>SANE</B> homepage (<I>http://www.sane-</I>
<I>project.org/</I>). Information about other frontends and backends can also
be found on the <B>SANE</B> homepage.
can be downloaded from the <B>SANE</B> homepage
(<I>http://www.sane-project.org/</I>). Information about other frontends and
backends can also be found on the <B>SANE</B> homepage.
</PRE>
@ -58,14 +58,15 @@
information about several aspects of <B>SANE.</B> A name with a number in
parenthesis (e.g. '<B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>') points to a manual page. In this case
'<B>man</B> <B>5</B> <B>sane-dll</B>' will display the page. Entries like
'<I>/usr/doc/sane-1.0.19/sane.tex</I>' are references to text files that were
copied to the <B>SANE</B> documentation directory (<I>/usr/doc/sane-1.0.19/</I>) dur-
ing installation. Everything else is a URL to a resource on the web.
'<I>/usr/doc/sane-1.0.20/sane.tex</I>' are references to text files that
were copied to the <B>SANE</B> documentation directory
(<I>/usr/doc/sane-1.0.20/</I>) during installation. Everything else is a
URL to a resource on the web.
<B>SANE</B> <B>homepage</B>
Information on all aspects of SANE including a tutorial and a link to
the SANE FAQ can be found on the SANE homepage: <I>http://www.sane-</I>
<I>project.org/</I>.
the SANE FAQ can be found on the SANE homepage:
<I>http://www.sane-project.org/</I>.
<B>SANE</B> <B>device</B> <B>lists</B>
The <B>SANE</B> device lists contain information about the status of <B>SANE</B>
@ -74,14 +75,14 @@
CAN YOU HELP SANE for details. There are lists for specific releases
of SANE, for the current development version and a search engine:
<I>http://www.sane-project.org/sane-supported-devices.html</I>. The lists
are also installed on your system at /usr/doc/sane-1.0.19/.
are also installed on your system at /usr/doc/sane-1.0.20/.
<B>SANE</B> <B>mailing</B> <B>list</B>
There is a mailing list for the purpose of discussing the SANE stan-
dard and its implementations: sane-devel. Despite its name, the list
is not only intended for developers, but also for users. There are
also some more lists for special topics, however, for users, sane-
devel is the right list. How to subscribe and unsubscribe:
also some more lists for special topics, however, for users,
sane-devel is the right list. How to subscribe and unsubscribe:
<I>http://www.sane-project.org/mailing-lists.html</I>.
<B>SANE</B> <B>IRC</B> <B>channel</B>
@ -94,12 +95,12 @@
server, etc.).
<B>Compiling</B> <B>and</B> <B>installing</B> <B>SANE</B>
Look at <I>/usr/doc/sane-1.0.19/README</I> and the os-dependent README files
for information about compiling and installing <B>SANE.</B>
Look at <I>/usr/doc/sane-1.0.20/README</I> and the os-dependent README
files for information about compiling and installing <B>SANE.</B>
<B>SCSI</B> <B>configuration</B>
For information about various systems and SCSI controllers see <B>sane-</B>
<B><A HREF="scsi.5.html">scsi(5)</A></B>.
For information about various systems and SCSI controllers see
<B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>.
<B>USB</B> <B>configuration</B>
For information about USB configuration see <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>.
@ -136,8 +137,8 @@
<B>apple</B>
The SANE backend for Apple flatbed scanners supports the following
scanners: AppleScanner, OneScanner and ColorOneScanner. See <B>sane-</B>
<B><A HREF="apple.5.html">apple(5)</A></B> for details.
scanners: AppleScanner, OneScanner and ColorOneScanner. See
<B><A HREF="sane-apple.5.html">sane-apple(5)</A></B> for details.
<B>artec</B>
The SANE Artec backend supports several Artec/Ultima SCSI flatbed
@ -180,12 +181,12 @@
ner. See <B><A HREF="sane-cardscan.5.html">sane-cardscan(5)</A></B> for details.
<B>coolscan</B>
This is a SANE backend for Nikon Coolscan film-scanners. See <B>sane-</B>
<B><A HREF="coolscan.5.html">coolscan(5)</A></B> for details.
This is a SANE backend for Nikon Coolscan film-scanners. See
<B><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B> for details.
<B>coolscan2</B>
This is a SANE backend for Nikon Coolscan film-scanners. See <B>sane-</B>
<B><A HREF="coolscan2.5.html">coolscan2(5)</A></B> or <I>http://coolscan2.sourceforge.net</I> for details.
This is a SANE backend for Nikon Coolscan film-scanners. See
<B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B> or <I>http://coolscan2.sourceforge.net</I> for details.
<B>epjitsu</B>
The epjitsu backend provides support for Epson-based Fujitsu USB
@ -214,8 +215,8 @@
<B>hp</B>
The SANE hp backend provides access to Hewlett-Packard ScanJet scan-
ners which support SCL (Scanner Control Language by HP). See <B>sane-</B>
<B><A HREF="hp.5.html">hp(5)</A></B> for details.
ners which support SCL (Scanner Control Language by HP). See
<B><A HREF="sane-hp.5.html">sane-hp(5)</A></B> for details.
<B>hpsj5s</B>
The SANE backend for the Hewlett-Packard ScanJet 5S scanner. See
@ -246,8 +247,8 @@
<B><A HREF="sane-hs2p.5.html">sane-hs2p(5)</A></B> for details.
<B>ibm</B>
The SANE backend for some IBM and Ricoh SCSI scanners. See <B>sane-</B>
<B><A HREF="ibm.5.html">ibm(5)</A></B> for details.
The SANE backend for some IBM and Ricoh SCSI scanners. See
<B><A HREF="sane-ibm.5.html">sane-ibm(5)</A></B> for details.
<B>leo</B>
This backend supports the Leo S3 and the Across FS-1130, which is a
@ -277,8 +278,8 @@
<B>mustek</B>
The SANE mustek backend supports most Mustek SCSI flatbed scanners
including the Paragon and ScanExpress series and the 600 II N and 600
II EP (non-SCSI). Some Trust scanners are also supported. See <B>sane-</B>
<B><A HREF="mustek.5.html">mustek(5)</A></B> for details.
II EP (non-SCSI). Some Trust scanners are also supported. See
<B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B> for details.
<B>mustek_pp</B>
The mustek_pp backend provides access to Mustek parallel port flatbed
@ -337,8 +338,8 @@
scanner. See <B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B> for details.
<B>sharp</B>
The SANE sharp backend supports Sharp SCSI scanners. See <B>sane-</B>
<B><A HREF="sharp.5.html">sharp(5)</A></B> for details.
The SANE sharp backend supports Sharp SCSI scanners. See
<B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B> for details.
<B>sm3600</B>
The SANE sm3600 backend supports the Microtek ScanMaker 3600 USB
@ -385,12 +386,12 @@
<B>umax1200u</B>
The sane-umax1220u backend supports the UMAX Astra 1220U (USB)
flatbed scanner (and also the UMAX Astra 2000U, sort of). See <B>sane-</B>
<B><A HREF="umax1220u.5.html">umax1220u(5)</A></B> for details.
flatbed scanner (and also the UMAX Astra 2000U, sort of). See
<B><A HREF="sane-umax1220u.5.html">sane-umax1220u(5)</A></B> for details.
Also, have a look at the backend information page at <I>http://www.sane-</I>
<I>project.org/sane-supported-devices.html</I> and the list of projects in
<I>/usr/doc/sane-1.0.19/PROJECTS</I>.
Also, have a look at the backend information page at
<I>http://www.sane-project.org/sane-supported-devices.html</I> and the list of
projects in <I>/usr/doc/sane-1.0.20/PROJECTS</I>.
</PRE>
@ -422,9 +423,9 @@
The sane-st680 backend provides access to webcams with a stv680 chip.
See <B><A HREF="sane-st680.5.html">sane-st680(5)</A></B> for details.
Also, have a look at the backend information page at <I>http://www.sane-</I>
<I>project.org/sane-supported-devices.html</I> and the list of projects in
<I>/usr/doc/sane-1.0.19/PROJECTS</I>.
Also, have a look at the backend information page at
<I>http://www.sane-project.org/sane-supported-devices.html</I> and the list of
projects in <I>/usr/doc/sane-1.0.20/PROJECTS</I>.
</PRE>
@ -436,8 +437,8 @@
<B>net</B>
The <B>SANE</B> network daemon saned provides access to scanners located on
different computers in connection with the net backend. See <B>sane-</B>
<B><A HREF="net.5.html">net(5)</A></B> and <B><A HREF="saned.8.html">saned(8)</A></B>.
different computers in connection with the net backend. See
<B><A HREF="sane-net.5.html">sane-net(5)</A></B> and <B><A HREF="saned.8.html">saned(8)</A></B>.
<B>pnm</B>
PNM image reader pseudo-backend. The purpose of this backend is pri-
@ -451,17 +452,17 @@
<B>test</B>
The <B>SANE</B> test backend is for testing frontends and the <B>SANE</B> installa-
tion. It provides test pictures and various test options. See <B>sane-</B>
<B><A HREF="test.5.html">test(5)</A></B>.
tion. It provides test pictures and various test options. See
<B><A HREF="sane-test.5.html">sane-test(5)</A></B>.
<B>v4l</B>
The sane-v4l library implements a <B>SANE</B> backend that provides generic
access to video cameras and similar equipment using the <B>V4L</B> (Video
for Linux) API. See <B><A HREF="sane-v4l.5.html">sane-v4l(5)</A></B><B>.</B>
Also, have a look at the backend information page at <I>http://www.sane-</I>
<I>project.org/sane-supported-devices.html</I> and the list of projects in
<I>/usr/doc/sane-1.0.19/PROJECTS</I>.
Also, have a look at the backend information page at
<I>http://www.sane-project.org/sane-supported-devices.html</I> and the list of
projects in <I>/usr/doc/sane-1.0.20/PROJECTS</I>.
</PRE>
@ -482,17 +483,18 @@
The <B>SANE</B> standard defines the application programming interface (API)
that is used to communicate between frontends and backends. It can be
found at <I>/usr/doc/sane-1.0.19/sane.ps</I> (if latex is installed on your
found at <I>/usr/doc/sane-1.0.20/sane.ps</I> (if latex is installed on your
system) and on the <B>SANE</B> website: <I>http://www.sane-project.org/html/</I>
(HTML), or <I>http://www.sane-project.org/sane.ps</I> (Postscript).
There is some more information for programmers in
<I>/usr/doc/sane-1.0.19/backend-writing.txt</I>. Most of the internal <B>SANE</B>
routines (<B>sanei</B>) are documented using doxygen: <I>http://www.sane-</I>
<I>project.org/sanei/</I>. Before a new backend or frontend project is
started, have a look at <I>/usr/doc/sane-1.0.19/PROJECTS</I> for projects that
are planned or not yet included into the <B>SANE</B> distribution and at our
bug-tracking system: <I>http://www.http://www.sane-project.org/bugs.html</I>.
<I>/usr/doc/sane-1.0.20/backend-writing.txt</I>. Most of the internal <B>SANE</B>
routines (<B>sanei</B>) are documented using doxygen:
<I>http://www.sane-project.org/sanei/</I>. Before a new backend or frontend
project is started, have a look at <I>/usr/doc/sane-1.0.20/PROJECTS</I> for
projects that are planned or not yet included into the <B>SANE</B> distribu-
tion and at our bug-tracking system:
<I>http://www.http://www.sane-project.org/bugs.html</I>.
There are some links on how to find out about the protocol of a scan-
ner: <I>http://www.meier-geinitz.de/sane/misc/develop.html</I>.
@ -514,7 +516,7 @@
The shared libraries implementing the backends (present on sys-
tems that support dynamic loading).
<I>/usr/doc/sane-1.0.19/*</I>
<I>/usr/doc/sane-1.0.20/*</I>
<B>SANE</B> documentation: The standard, READMEs, text files for back-
ends etc.
@ -604,42 +606,43 @@
For reporting bugs or requesting new features, please use our bug-
tracking system: <I>http://www.sane-project.org/bugs.html</I>. You can also
contact the author of your backend directly. Usually the email address
can be found in the <I>/usr/doc/sane-1.0.19/AUTHORS</I> file or the backend's
manpage. For general discussion about SANE, please use the <B>SANE</B> mailing
list sane-devel (see <I>http://www.sane-project.org/mailing-lists.html</I> for
details).
can be found in the <I>/usr/doc/sane-1.0.20/AUTHORS</I> file or the back-
end's manpage. For general discussion about SANE, please use the <B>SANE</B>
mailing list sane-devel (see <I>http://www.sane-project.org/mail-</I>
<I>ing-lists.html</I> for details).
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="saned.8.html">saned(8)</A></B>, <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="sane-abaton.5.html">sane-abaton(5)</A></B>, <B>sane-</B>
<B><A HREF="agfafocus.5.html">agfafocus(5)</A></B>, <B><A HREF="sane-apple.5.html">sane-apple(5)</A></B>, <B><A HREF="sane-artec.5.html">sane-artec(5)</A></B>, <B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B>,
<B><A HREF="sane-as6e.5.html">sane-as6e(5)</A></B>, <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B>, <B><A HREF="sane-bh.5.html">sane-bh(5)</A></B>, <B><A HREF="sane-canon.5.html">sane-canon(5)</A></B>, <B>sane-</B>
<B><A HREF="canon630u.5.html">canon630u(5)</A></B>, <B><A HREF="sane-canon_pp.5.html">sane-canon_pp(5)</A></B>, <B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B>, <B><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B>,
<B><A HREF="sane-dc210.5.html">sane-dc210(5)</A></B>, <B><A HREF="sane-dc240.5.html">sane-dc240(5)</A></B>, <B><A HREF="sane-dc25.5.html">sane-dc25(5)</A></B>, <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>, <B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B>,
<B><A HREF="sane-epson.5.html">sane-epson(5)</A></B>, <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>, <B><A HREF="sane-genesys.5.html">sane-genesys(5)</A></B>, <B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>, <B>sane-</B>
<B><A HREF="gt68xx.5.html">gt68xx(5)</A></B>, <B><A HREF="sane-hp.5.html">sane-hp(5)</A></B>, <B><A HREF="sane-hpsj5s.5.html">sane-hpsj5s(5)</A></B>, <B><A HREF="sane-hp3500.5.html">sane-hp3500(5)</A></B>, <B><A HREF="sane-hp3900.5.html">sane-hp3900(5)</A></B>,
<B><A HREF="sane-hp4200.5.html">sane-hp4200(5)</A></B>, <B><A HREF="sane-hp5400.5.html">sane-hp5400(5)</A></B>, <B><A HREF="sane-hpljm1005.5.html">sane-hpljm1005(5)</A></B>, <B><A HREF="sane-ibm.5.html">sane-ibm(5)</A></B>, <B>sane-</B>
<B><A HREF="leo.5.html">leo(5)</A></B>, <B><A HREF="sane-lexmark.5.html">sane-lexmark(5)</A></B>, <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>, <B><A HREF="sane-matsushita.5.html">sane-matsushita(5)</A></B>, <B>sane-</B>
<B><A HREF="microtek2.5.html">microtek2(5)</A></B>, <B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>,
<B><A HREF="saned.8.html">saned(8)</A></B>, <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="sane-abaton.5.html">sane-abaton(5)</A></B>,
<B><A HREF="sane-agfafocus.5.html">sane-agfafocus(5)</A></B>, <B><A HREF="sane-apple.5.html">sane-apple(5)</A></B>, <B><A HREF="sane-artec.5.html">sane-artec(5)</A></B>,
<B><A HREF="sane-artec_eplus48u.5.html">sane-artec_eplus48u(5)</A></B>, <B><A HREF="sane-as6e.5.html">sane-as6e(5)</A></B>, <B><A HREF="sane-avision.5.html">sane-avision(5)</A></B>, <B><A HREF="sane-bh.5.html">sane-bh(5)</A></B>,
<B><A HREF="sane-canon.5.html">sane-canon(5)</A></B>, <B><A HREF="sane-canon630u.5.html">sane-canon630u(5)</A></B>, <B><A HREF="sane-canon_pp.5.html">sane-canon_pp(5)</A></B>, <B><A HREF="sane-coolscan2.5.html">sane-coolscan2(5)</A></B>,
<B><A HREF="sane-coolscan.5.html">sane-coolscan(5)</A></B>, <B><A HREF="sane-dc210.5.html">sane-dc210(5)</A></B>, <B><A HREF="sane-dc240.5.html">sane-dc240(5)</A></B>, <B><A HREF="sane-dc25.5.html">sane-dc25(5)</A></B>,
<B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>, <B><A HREF="sane-dmc.5.html">sane-dmc(5)</A></B>, <B><A HREF="sane-epson.5.html">sane-epson(5)</A></B>, <B><A HREF="sane-fujitsu.5.html">sane-fujitsu(5)</A></B>,
<B><A HREF="sane-genesys.5.html">sane-genesys(5)</A></B>, <B><A HREF="sane-gphoto2.5.html">sane-gphoto2(5)</A></B>, <B><A HREF="sane-gt68xx.5.html">sane-gt68xx(5)</A></B>, <B><A HREF="sane-hp.5.html">sane-hp(5)</A></B>,
<B><A HREF="sane-hpsj5s.5.html">sane-hpsj5s(5)</A></B>, <B><A HREF="sane-hp3500.5.html">sane-hp3500(5)</A></B>, <B><A HREF="sane-hp3900.5.html">sane-hp3900(5)</A></B>, <B><A HREF="sane-hp4200.5.html">sane-hp4200(5)</A></B>,
<B><A HREF="sane-hp5400.5.html">sane-hp5400(5)</A></B>, <B><A HREF="sane-hpljm1005.5.html">sane-hpljm1005(5)</A></B>, <B><A HREF="sane-ibm.5.html">sane-ibm(5)</A></B>, <B><A HREF="sane-leo.5.html">sane-leo(5)</A></B>, <B>sane-lex-</B>
<B><A HREF="mark.5.html">mark(5)</A></B>, <B><A HREF="sane-ma1509.5.html">sane-ma1509(5)</A></B>, <B><A HREF="sane-matsushita.5.html">sane-matsushita(5)</A></B>, <B><A HREF="sane-microtek2.5.html">sane-microtek2(5)</A></B>,
<B><A HREF="sane-microtek.5.html">sane-microtek(5)</A></B>, <B><A HREF="sane-mustek.5.html">sane-mustek(5)</A></B>, <B><A HREF="sane-mustek_pp.5.html">sane-mustek_pp(5)</A></B>,
<B><A HREF="sane-mustek_usb.5.html">sane-mustek_usb(5)</A></B>, <B><A HREF="sane-mustek_usb2.5.html">sane-mustek_usb2(5)</A></B>, <B><A HREF="sane-nec.5.html">sane-nec(5)</A></B>, <B><A HREF="sane-net.5.html">sane-net(5)</A></B>,
<B><A HREF="sane-niash.5.html">sane-niash(5)</A></B>, <B><A HREF="sane-pie.5.html">sane-pie(5)</A></B>, <B><A HREF="sane-pint.5.html">sane-pint(5)</A></B>, <B><A HREF="sane-plustek.5.html">sane-plustek(5)</A></B>, <B>sane-plus-</B>
<B><A HREF="tek_pp.5.html">tek_pp(5)</A></B>, <B><A HREF="sane-pnm.5.html">sane-pnm(5)</A></B>, <B><A HREF="sane-qcam.5.html">sane-qcam(5)</A></B>, <B><A HREF="sane-ricoh.5.html">sane-ricoh(5)</A></B>, <B><A HREF="sane-s9036.5.html">sane-s9036(5)</A></B>,
<B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B>, <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B>, <B>sane-</B>
<B><A HREF="sm3840.5.html">sm3840(5)</A></B>, <B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B>, <B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B>, <B><A HREF="sane-st400.5.html">sane-st400(5)</A></B>, <B>sane-</B>
<B><A HREF="stv680.5.html">stv680(5)</A></B>, <B><A HREF="sane-tamarack.5.html">sane-tamarack(5)</A></B>, <B><A HREF="sane-teco1.5.html">sane-teco1(5)</A></B>, <B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B>, <B>sane-</B>
<B><A HREF="teco3.5.html">teco3(5)</A></B>, <B><A HREF="sane-test.5.html">sane-test(5)</A></B>, <B><A HREF="sane-u12.5.html">sane-u12(5)</A></B>, <B><A HREF="sane-umax1220u.5.html">sane-umax1220u(5)</A></B>, <B><A HREF="sane-umax.5.html">sane-umax(5)</A></B>,
<B><A HREF="sane-umax_pp.5.html">sane-umax_pp(5)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-v4l.5.html">sane-v4l(5)</A></B>
<B><A HREF="sane-sceptre.5.html">sane-sceptre(5)</A></B>, <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>, <B><A HREF="sane-sharp.5.html">sane-sharp(5)</A></B>, <B><A HREF="sane-sm3600.5.html">sane-sm3600(5)</A></B>,
<B><A HREF="sane-sm3840.5.html">sane-sm3840(5)</A></B>, <B><A HREF="sane-snapscan.5.html">sane-snapscan(5)</A></B>, <B><A HREF="sane-sp15c.5.html">sane-sp15c(5)</A></B>, <B><A HREF="sane-st400.5.html">sane-st400(5)</A></B>,
<B><A HREF="sane-stv680.5.html">sane-stv680(5)</A></B>, <B><A HREF="sane-tamarack.5.html">sane-tamarack(5)</A></B>, <B><A HREF="sane-teco1.5.html">sane-teco1(5)</A></B>, <B><A HREF="sane-teco2.5.html">sane-teco2(5)</A></B>,
<B><A HREF="sane-teco3.5.html">sane-teco3(5)</A></B>, <B><A HREF="sane-test.5.html">sane-test(5)</A></B>, <B><A HREF="sane-u12.5.html">sane-u12(5)</A></B>, <B><A HREF="sane-umax1220u.5.html">sane-umax1220u(5)</A></B>,
<B><A HREF="sane-umax.5.html">sane-umax(5)</A></B>, <B><A HREF="sane-umax_pp.5.html">sane-umax_pp(5)</A></B>, <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>, <B><A HREF="sane-v4l.5.html">sane-v4l(5)</A></B>
</PRE>
<H2>AUTHOR</H2><PRE>
David Mosberger-Tang and many many more (see
<I>/usr/doc/sane-1.0.19/AUTHORS</I> for details). This man page was written
by Henning Meier-Geinitz. Quite a lot of text was taken from the <B>SANE</B>
standard, several man pages, and README files.
<I>/usr/doc/sane-1.0.20/AUTHORS</I> for details). This man page was writ-
ten by Henning Meier-Geinitz. Quite a lot of text was taken from the
<B>SANE</B> standard, several man pages, and README files.
sane-backends 1.0.19 16 October 2005 <B><A HREF="sane.7.html">sane(7)</A></B>
14 Jul 2008 <B><A HREF="sane.7.html">sane(7)</A></B>
</PRE>
<HR>
<ADDRESS>

186
man/saned.1.html
Wyświetl plik

@ -1,186 +0,0 @@
<HTML>
<HEAD>
<TITLE>saned.1</TITLE>
</HEAD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="/images/sane.png" HEIGHT=117 WIDTH=346></H1>
<H1>saned.1</H1>
<HR>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
<B><A HREF="saned.1.html">saned(1)</A></B> SANE Scanner Access Now Easy <B><A HREF="saned.1.html">saned(1)</A></B>
</PRE>
<H2>NAME</H2><PRE>
saned - SANE network daemon
</PRE>
<H2>SYNOPSIS</H2><PRE>
<B>saned</B> [<B>-d</B>|<B>-s</B> [<I>n</I>]]
</PRE>
<H2>DESCRIPTION</H2><PRE>
<B>saned</B> is the SANE (Scanner Access Now Easy) daemon that allows remote
clients to access image acquisition devices available on the local
host.
</PRE>
<H2>OPTIONS</H2><PRE>
The <B>-d</B> and <B>-s</B> flags request that <B>saned</B> run in debug mode (as opposed to
<B><A HREF="inetd.8.html">inetd(8)</A></B> mode). In this mode, <B>saned</B> explicitly waits for a connection
request. When compiled with debugging enabled, these flags may be fol-
lowed by a number to request debug info. The larger the number, the
more verbose the debug output. E.g., <B>-d128</B> will request printing of
all debug info. Debug level 0 means no debug output at all. The default
value is 2. If flag <B>-d</B> is used, the debug messages will be printed to
stderr while <B>-s</B> requests using syslog.
If <B>saned</B> is run from inetd or xinetd, no option can be given.
</PRE>
<H2>CONFIGURATION</H2><PRE>
First and foremost: <B>saned</B> is not intended to be exposed to the internet
or other non-trusted networks. Make sure that access is limited by tcp-
wrappers and/or a firewall setup. Don't depend only on <B>saned</B>'s own
authentification. Don't run <B>saned</B> as root if it's not necessary. And do
<B>not</B> install <B>saned</B> as setuid root.
The contents of the <I>saned.conf</I> file is a list of host names, IP
addresses or IP subnets (CIDR notation) that are permitted to use local
SANE devices. IPv6 addresses must be enclosed in brackets, and should
always be specified in their compressed form. Connections from local-
host are always permitted. Empty lines and lines starting with a hash
mark (#) are ignored. A line containing the single character ``+'' is
interpreted to match any hostname. This allows any remote machine to
use your scanner and may present a security risk, so this shouldn't be
used unless you know what you're doing. A sample configuration file is
shown below:
scan-client.somedomain.firm
# this is a comment
192.168.0.1
192.168.2.12/29
[::1]
[2001:7a8:185e::42:12]/64
The case of the host names does not matter, so AHost.COM is considered
identical to ahost.com.
For <B>saned</B> to work properly, it is also necessary to add a configuration
line to <I>/etc/inetd.conf</I>. Note that your inetd must support IPv6 if you
want to connect to saned over IPv6 ; xinetd and openbsd-inetd are known
to support IPv6, check the documentation for your inetd daemon.
The configuration line normally looks like this:
sane stream tcp nowait saned.saned /usr/local/sbin/saned saned
However, if your system uses <B><A HREF="tcpd.8.html">tcpd(8)</A></B> for additional security screening,
you may want to disable saned access control by putting ``+'' in
<I>saned.conf</I> and use a line of the following form in <I>/etc/inetd.conf</I>
instead:
sane stream tcp nowait saned.saned /usr/sbin/tcpd
/usr/local/sbin/saned
Note that both examples assume that there is a <B>saned</B> group and a <B>saned</B>
user. If you follow this example, please make sure that the access
permissions on the special device are set such that <B>saned</B> can access
the scanner (the program generally needs read and write access to scan-
ner devices).
If xinetd is installed on your system instead of inetd the following
example for xinetd.conf may be helpful:
# default: off
# description: The sane server accepts requests
# for network access to a local scanner via the
# network.
service sane
{
port = 6566
socket_type = stream
wait = no
user = saned
group = saned
server = /usr/local/sbin/saned
}
Finally, it is also necessary to add a line of the following form to
<I>/etc/services</I>:
sane 6566/tcp # SANE network scanner daemon
</PRE>
<H2>RESTRICTIONS</H2><PRE>
In addition to the control connection (port 6566) saned also uses a
data connection. The port of this socket is selected by the operating
system and can't be specified by the user currently. This may be a
problem if the connection must go through a firewall (packet filter).
If you must use a packet filter, make sure that all ports &gt; 1024 are
open on the server for connections from the client.
</PRE>
<H2>FILES</H2><PRE>
<I>/etc/hosts.equiv</I>
The hosts listed in this file are permitted to access all local
SANE devices. Caveat: this file imposes serious security risks
and its use is not recommended.
<I>/usr/local/etc/sane.d/saned.conf</I>
Contains a list of hosts permitted to access local SANE devices
(see also description of <B>SANE_CONFIG_DIR</B> below).
<I>/usr/local/etc/sane.d/saned.users</I>
If this file contains lines of the form
user:password:backend
access to the listed backends is restricted. A backend may be
listed multiple times for different user/password combinations.
The server uses MD5 encryption if supported by the client.
</PRE>
<H2>ENVIRONMENT</H2><PRE>
<B>SANE_CONFIG_DIR</B>
This environment variable specifies the list of directories that
may contain the configuration file. Under UNIX, the directories
are separated by a colon (`:'), under OS/2, they are separated
by a semi-colon (`;'). If this variable is not set, the config-
uration file is searched in two default directories: first, the
current working directory (".") and then in
/usr/local/etc/sane.d. If the value of the environment variable
ends with the directory separator character, then the default
directories are searched after the explicitly specified directo-
ries. For example, setting <B>SANE_CONFIG_DIR</B> to "/tmp/config:"
would result in directories "tmp/config", ".", and
"/usr/local/etc/sane.d" being searched (in this order).
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, <B><A HREF="xcam.1.html">xcam(1)</A></B>, <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>, <B>sane-</B>
<B><A HREF="net.5.html">net(5)</A></B>, <B>sane-"backendname"</B>(5)
<I>http://www.penguin-breeder.org/?page=sane-net</I>
</PRE>
<H2>AUTHOR</H2><PRE>
David Mosberger
sane-backends 1.0.14-cvs 29 Oct 2003 <B><A HREF="saned.1.html">saned(1)</A></B>
</PRE>
<HR>
<ADDRESS>
Man(1) output converted with
<a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a>
</ADDRESS>
</BODY>
</HTML>

75
man/saned.8.html
Wyświetl plik

@ -17,7 +17,7 @@
</PRE>
<H2>SYNOPSIS</H2><PRE>
<B>saned</B> [<B>-d</B>|<B>-s</B> [<I>n</I>]]
<B>saned</B> <B>[</B> <B>-a</B> <I>[</I> <I>username</I> <I>]</I> <B>|</B> <B>-d</B> <I>[</I> <I>n</I> <I>]</I> <B>|</B> <B>-s</B> <I>[</I> <I>n</I> <I>]</I> <B>]</B>
</PRE>
@ -29,6 +29,12 @@
</PRE>
<H2>OPTIONS</H2><PRE>
The <B>-a</B> flag requests that <B>saned</B> run in standalone daemon mode. In this
mode, <B>saned</B> will detach from the console and run in the background,
listening for incoming client connections; <B>inetd</B> is not required for
<B>saned</B> operations in this mode. If the optional <B>username</B> is given after
<B>-a</B> , <B>saned</B> will drop root privileges and run as this user (and group).
The <B>-d</B> and <B>-s</B> flags request that <B>saned</B> run in debug mode (as opposed to
<B><A HREF="inetd.8.html">inetd(8)</A></B> mode). In this mode, <B>saned</B> explicitly waits for a connection
request. When compiled with debugging enabled, these flags may be fol-
@ -46,20 +52,35 @@
First and foremost: <B>saned</B> is not intended to be exposed to the internet
or other non-trusted networks. Make sure that access is limited by tcp-
wrappers and/or a firewall setup. Don't depend only on <B>saned</B>'s own
authentification. Don't run <B>saned</B> as root if it's not necessary. And do
authentication. Don't run <B>saned</B> as root if it's not necessary. And do
<B>not</B> install <B>saned</B> as setuid root.
The contents of the <I>saned.conf</I> file is a list of host names, IP
addresses or IP subnets (CIDR notation) that are permitted to use local
SANE devices. IPv6 addresses must be enclosed in brackets, and should
always be specified in their compressed form. Connections from local-
host are always permitted. Empty lines and lines starting with a hash
mark (#) are ignored. A line containing the single character ''+'' is
interpreted to match any hostname. This allows any remote machine to
use your scanner and may present a security risk, so this shouldn't be
used unless you know what you're doing. A sample configuration file is
shown below:
The <I>saned.conf</I> configuration file contains both options for the daemon
and the access list.
<B>data_portrange</B> = <I>min</I><B>_</B><I>port</I> - <I>max</I><B>_</B><I>port</I>
Specify the port range to use for the data connection. Pick a
port range between 1024 and 65535; don't pick a too large port
range, as it may have performance issues. Use this option if
your <B>saned</B> server is sitting behind a firewall. If that firewall
is a Linux machine, we strongly recommend using the Netfilter
<I>nf</I><B>_</B><I>conntrack</I><B>_</B><I>sane</I> module instead.
The access list is a list of host names, IP addresses or IP subnets
(CIDR notation) that are permitted to use local SANE devices. IPv6
addresses must be enclosed in brackets, and should always be specified
in their compressed form. Connections from localhost are always permit-
ted. Empty lines and lines starting with a hash mark (#) are ignored. A
line containing the single character ''+'' is interpreted to match any
hostname. This allows any remote machine to use your scanner and may
present a security risk, so this shouldn't be used unless you know what
you're doing.
A sample configuration file is shown below:
# Daemon options
data_portrange = 10000 - 10100
# Access list
scan-client.somedomain.firm
# this is a comment
192.168.0.1
@ -70,10 +91,14 @@
The case of the host names does not matter, so AHost.COM is considered
identical to ahost.com.
For <B>saned</B> to work properly, it is also necessary to add a configuration
line to <I>/etc/inetd.conf</I>. Note that your inetd must support IPv6 if you
want to connect to saned over IPv6 ; xinetd and openbsd-inetd are known
to support IPv6, check the documentation for your inetd daemon.
</PRE>
<H2>INETD CONFIGURATION</H2><PRE>
For <B>saned</B> to work properly in its default mode of operation, it is also
necessary to add a configuration line to <I>/etc/inetd.conf</I>. Note that
your inetd must support IPv6 if you want to connect to saned over IPv6
; xinetd and openbsd-inetd are known to support IPv6, check the docu-
mentation for your inetd daemon.
The configuration line normally looks like this:
@ -119,16 +144,6 @@
name "sane" is now deprecated.
</PRE>
<H2>RESTRICTIONS</H2><PRE>
In addition to the control connection (port 6566) saned also uses a
data connection. The port of this socket is selected by the operating
system and can't be specified by the user currently. This may be a
problem if the connection must go through a firewall (packet filter).
If you must use a packet filter, make sure that all ports &gt; 1024 are
open on the server for connections from the client.
</PRE>
<H2>FILES</H2><PRE>
<I>/etc/hosts.equiv</I>
@ -147,7 +162,7 @@
access to the listed backends is restricted. A backend may be
listed multiple times for different user/password combinations.
The server uses MD5 encryption if supported by the client.
The server uses MD5 hashing if supported by the client.
</PRE>
@ -169,8 +184,8 @@
</PRE>
<H2>SEE ALSO</H2><PRE>
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, <B><A HREF="xcam.1.html">xcam(1)</A></B>, <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>, <B>sane-</B>
<B><A HREF="net.5.html">net(5)</A></B>, <B>sane-"backendname"</B>(5)
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="scanimage.1.html">scanimage(1)</A></B>, <B><A HREF="xscanimage.1.html">xscanimage(1)</A></B>, <B><A HREF="xcam.1.html">xcam(1)</A></B>, <B><A HREF="sane-dll.5.html">sane-dll(5)</A></B>,
<B><A HREF="sane-net.5.html">sane-net(5)</A></B>, <B>sane-"backendname"</B>(5)
<I>http://www.penguin-breeder.org/?page=sane-net</I>
@ -178,7 +193,7 @@
<H2>AUTHOR</H2><PRE>
David Mosberger
sane-backends 1.0.19 30 May 2004 <B><A HREF="saned.8.html">saned(8)</A></B>
20 Apr 2009 <B><A HREF="saned.8.html">saned(8)</A></B>
</PRE>
<HR>
<ADDRESS>

2
sane-frontends.html
Wyświetl plik

@ -156,7 +156,7 @@
sane-frontends). Unlike xscanimage it acquires images continuously.
</li>
<li>
<a href="http://www.epkowa.co.jp/english/linux_e/lsd_e.html" target="_top">Image Scan! for Linux</a>
<a href="http://www.avasys.jp/lx-bin2/linux_e/scan/DL1.do" target="_top">Image Scan! for Linux</a>
- graphical frontend for Epson scanners
</li>
</ul>