From 76b72727a367152de58ef467aec27e3304c25781 Mon Sep 17 00:00:00 2001 From: "m. allan noah" Date: Wed, 10 Feb 2010 10:23:52 -0500 Subject: [PATCH] update old manpages, change iscan link --- man/sane.7.html | 455 ++++++++++++++++++++++---------------------- man/saned.1.html | 186 ------------------ man/saned.8.html | 101 +++++----- sane-frontends.html | 2 +- 4 files changed, 288 insertions(+), 456 deletions(-) delete mode 100644 man/saned.1.html diff --git a/man/sane.7.html b/man/sane.7.html index c24910ab..bb68daf1 100644 --- a/man/sane.7.html +++ b/man/sane.7.html @@ -47,9 +47,9 @@ (including the SANE standard), networking support, and the command line frontend 'scanimage'. The frontends 'xscanimage', 'xcam', and 'scanadf' are included in the package 'sane-frontends'. Both packages - can be downloaded from the SANE homepage (http://www.sane- - project.org/). Information about other frontends and backends can also - be found on the SANE homepage. + can be downloaded from the SANE homepage + (http://www.sane-project.org/). Information about other frontends and + backends can also be found on the SANE homepage. @@ -58,48 +58,49 @@ information about several aspects of SANE. A name with a number in parenthesis (e.g. 'sane-dll(5)') points to a manual page. In this case 'man 5 sane-dll' will display the page. Entries like - '/usr/doc/sane-1.0.19/sane.tex' are references to text files that were - copied to the SANE documentation directory (/usr/doc/sane-1.0.19/) dur- - ing installation. Everything else is a URL to a resource on the web. + '/usr/doc/sane-1.0.20/sane.tex' are references to text files that + were copied to the SANE documentation directory + (/usr/doc/sane-1.0.20/) during installation. Everything else is a + URL to a resource on the web. SANE homepage Information on all aspects of SANE including a tutorial and a link to - the SANE FAQ can be found on the SANE homepage: http://www.sane- - project.org/. + the SANE FAQ can be found on the SANE homepage: + http://www.sane-project.org/. SANE device lists - The SANE device lists contain information about the status of SANE - support for a specific device. If your scanner is not listed there + The SANE device lists contain information about the status of SANE + support for a specific device. If your scanner is not listed there (either supported or unsupported), please contact us. See section HOW - CAN YOU HELP SANE for details. There are lists for specific releases - of SANE, for the current development version and a search engine: + CAN YOU HELP SANE for details. There are lists for specific releases + of SANE, for the current development version and a search engine: http://www.sane-project.org/sane-supported-devices.html. 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/. SANE mailing list - There is a mailing list for the purpose of discussing the SANE stan- + 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: + 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: http://www.sane-project.org/mailing-lists.html. SANE IRC channel - The IRC (Internet Relay Chat) channel #sane can be found on the - Freenode network (irc.freenode.net). It's for discussing SANE prob- - lems, talking about development and general SANE related chatting. + The IRC (Internet Relay Chat) channel #sane can be found on the + Freenode network (irc.freenode.net). It's for discussing SANE prob- + lems, talking about development and general SANE related chatting. Before asking for help, please read the other documentation mentioned - in this manual page. The channel's topic is also used for announce- - ments of problems with SANE infrastructure (mailing lists, web + in this manual page. The channel's topic is also used for announce- + ments of problems with SANE infrastructure (mailing lists, web server, etc.). Compiling and installing SANE - Look at /usr/doc/sane-1.0.19/README and the os-dependent README files - for information about compiling and installing SANE. + Look at /usr/doc/sane-1.0.20/README and the os-dependent README + files for information about compiling and installing SANE. SCSI configuration - For information about various systems and SCSI controllers see sane- - scsi(5). + For information about various systems and SCSI controllers see + sane-scsi(5). USB configuration For information about USB configuration see sane-usb(5). @@ -115,10 +116,10 @@ sition devices available on the local host. See saned(8). sane-find-scanner - Command-line tool to find SCSI and USB scanners and determine their + Command-line tool to find SCSI and USB scanners and determine their Unix device files. See sane-find-scanner(1). - Also, have a look at the sane-frontends package (including xscanimage, + Also, have a look at the sane-frontends package (including xscanimage, xcam, and scanadf) and the frontend information page at http://www.sane-project.org/sane-frontends.html. @@ -127,68 +128,68 @@

BACKENDS FOR SCANNERS

        abaton
          The SANE backend for Abaton flatbed scanners supports the Scan 300/GS
-         (8bit,  256  levels  of  gray)  and  the Scan 300/S (black and white,
+         (8bit, 256 levels of gray) and  the  Scan  300/S  (black  and  white,
          untested). See sane-abaton(5) for details.
 
        agfafocus
-         This backend supports AGFA  Focus  scanners  and  the  Siemens  S9036
+         This  backend  supports  AGFA  Focus  scanners  and the Siemens S9036
          (untested).  See sane-agfafocus(5) for details.
 
        apple
-         The  SANE  backend  for Apple flatbed scanners supports the following
-         scanners: AppleScanner, OneScanner  and  ColorOneScanner.  See  sane-
-         apple(5) for details.
+         The SANE backend for Apple flatbed scanners  supports  the  following
+         scanners:   AppleScanner,   OneScanner   and   ColorOneScanner.   See
+         sane-apple(5) for details.
 
        artec
-         The  SANE  Artec  backend  supports several Artec/Ultima SCSI flatbed
-         scanners as well as the BlackWidow BW4800SP and the  Plustek  19200S.
+         The SANE Artec backend supports  several  Artec/Ultima  SCSI  flatbed
+         scanners  as  well as the BlackWidow BW4800SP and the Plustek 19200S.
          See sane-artec(5) for details.
 
        artec_eplus48u
          The SANE artec_eplus48u backend supports the scanner Artec E+ 48U and
-         re-badged models like Tevion MD 9693, Medion MD 9693, Medion MD  9705
+         re-badged  models like Tevion MD 9693, Medion MD 9693, Medion MD 9705
          and Trust Easy Webscan 19200. See sane-artec_eplus48u(5) for details.
 
        as6e
-         This is a SANE backend for using the Artec AS6E parallel port  inter-
+         This  is a SANE backend for using the Artec AS6E parallel port inter-
          face scanner. See sane-as6e(5) for details.
 
        avision
-         This  backend  supports several Avision based scanners. This includes
-         the original Avision scanners (like AV 630, AV 620, ...) as  well  as
-         the  HP  ScanJet 53xx and 74xx series, Fujitsu ScanPartner, some Mit-
-         subishi and Minolta film-scanners.  See sane-avision(5) for  details.
+         This backend supports several Avision based scanners.  This  includes
+         the  original  Avision scanners (like AV 630, AV 620, ...) as well as
+         the HP ScanJet 53xx and 74xx series, Fujitsu ScanPartner,  some  Mit-
+         subishi  and Minolta film-scanners.  See sane-avision(5) for details.
 
        bh
          The bh backend provides access to Bell+Howell Copiscan II series doc-
          ument scanners. See sane-bh(5) for details.
 
        canon
-         The canon backend  supports  the  CanoScan  300,  CanoScan  600,  and
-         CanoScan  2700F SCSI flatbed scanners. See sane-canon(5) for details.
+         The  canon  backend  supports  the  CanoScan  300,  CanoScan 600, and
+         CanoScan 2700F SCSI flatbed scanners. See sane-canon(5) for  details.
 
        canon630u
-         The canon630u backend supports the CanoScan 630u and 636u  USB  scan-
+         The  canon630u  backend supports the CanoScan 630u and 636u USB scan-
          ners.  See sane-canon630u(5) for details.
 
        canon_pp
-         The  canon_pp backend supports the CanoScan FB330P, FB630P, N340P and
+         The canon_pp backend supports the CanoScan FB330P, FB630P, N340P  and
          N640P parallel port scanners.  See sane-canon_pp(5) for details.
 
        cardscan
-         This backend provides support for the Corex Cardscan 800c  USB  scan-
+         This  backend  provides support for the Corex Cardscan 800c USB scan-
          ner. See sane-cardscan(5) for details.
 
        coolscan
-         This  is  a  SANE backend for Nikon Coolscan film-scanners. See sane-
-         coolscan(5) for details.
+         This  is  a  SANE  backend  for  Nikon  Coolscan  film-scanners.  See
+         sane-coolscan(5) for details.
 
        coolscan2
-         This is a SANE backend for Nikon Coolscan film-scanners.   See  sane-
-         coolscan2(5) or http://coolscan2.sourceforge.net for details.
+         This  is  a  SANE  backend  for  Nikon  Coolscan  film-scanners.  See
+         sane-coolscan2(5) or http://coolscan2.sourceforge.net for details.
 
        epjitsu
-         The  epjitsu  backend  provides  support  for Epson-based Fujitsu USB
+         The epjitsu backend provides  support  for  Epson-based  Fujitsu  USB
          scanners. See sane-epjitsu(5) for details.
 
        epson
@@ -196,89 +197,89 @@
          and USB flatbed scanners. See sane-epson(5) for details.
 
        fujitsu
-         The  fujitsu  backend provides support for most Fujitsu SCSI and USB,
+         The fujitsu backend provides support for most Fujitsu SCSI  and  USB,
          flatbed and adf scanners. See sane-fujitsu(5) for details.
 
        genesys
-         The genesys backend  provides  support  for  scanners  based  on  the
+         The  genesys  backend  provides  support  for  scanners  based on the
          Genesys Logic GL646 and GL841 chips like the Medion 6471 and Hewlett-
-         Packard 2300c.  Support for GL841 based scanners is  far  from  being
+         Packard  2300c.   Support  for GL841 based scanners is far from being
          complete. See sane-genesys(5) for details.
 
        gt68xx
-         The  gt68xx  backend  provides  support  for  scanners  based  on the
-         Grandtech GT-6801 and GT-6816 chips like the Artec  Ultima  2000  and
-         several  Mustek  BearPaw  CU  and  TA  models.  Some Genius, Lexmark,
+         The gt68xx  backend  provides  support  for  scanners  based  on  the
+         Grandtech  GT-6801  and  GT-6816 chips like the Artec Ultima 2000 and
+         several Mustek BearPaw  CU  and  TA  models.  Some  Genius,  Lexmark,
          Medion, Packard Bell, Plustek, and Trust scanners are also supported.
          See sane-gt68xx(5) for details.
 
        hp
-         The  SANE hp backend provides access to Hewlett-Packard ScanJet scan-
-         ners which support SCL (Scanner Control Language by  HP).  See  sane-
-         hp(5) for details.
+         The SANE hp backend provides access to Hewlett-Packard ScanJet  scan-
+         ners  which  support  SCL  (Scanner  Control  Language  by  HP).  See
+         sane-hp(5) for details.
 
        hpsj5s
-         The  SANE  backend  for  the  Hewlett-Packard ScanJet 5S scanner. See
+         The SANE backend for the  Hewlett-Packard  ScanJet  5S  scanner.  See
          sane-hpsj5s(5) for details.
 
        hp3500
-         The SANE backend for the Hewlett-Packard  ScanJet  3500  series.  See
+         The  SANE  backend  for  the Hewlett-Packard ScanJet 3500 series. See
          sane-hp3500(5) for details.
 
        hp3900
-         The  SANE  backend  for  the Hewlett-Packard ScanJet 3900 series. See
+         The SANE backend for the Hewlett-Packard  ScanJet  3900  series.  See
          sane-hp3900(5) for details.
 
        hp4200
-         The SANE backend for the Hewlett-Packard  ScanJet  4200  series.  See
+         The  SANE  backend  for  the Hewlett-Packard ScanJet 4200 series. See
          sane-hp4200(5) for details.
 
        hp5400
-         The  SANE  backend  for the Hewlett-Packard ScanJet 54XXC series. See
+         The SANE backend for the Hewlett-Packard ScanJet  54XXC  series.  See
          sane-hp5400(5) for details.
 
        hpljm1005
-         The SANE backend for the Hewlett-Packard LaserJet M1005 scanner.  See
+         The  SANE backend for the Hewlett-Packard LaserJet M1005 scanner. See
          sane-hpljm1005(5) for details.
 
        hs2p
-         The  SANE  backend  for  the Ricoh IS450 family of SCSI scanners. See
+         The SANE backend for the Ricoh IS450 family  of  SCSI  scanners.  See
          sane-hs2p(5) for details.
 
        ibm
-         The SANE backend for some IBM and  Ricoh  SCSI  scanners.  See  sane-
-         ibm(5) for details.
+         The   SANE  backend  for  some  IBM  and  Ricoh  SCSI  scanners.  See
+         sane-ibm(5) for details.
 
        leo
-         This  backend  supports the Leo S3 and the Across FS-1130, which is a
+         This backend supports the Leo S3 and the Across FS-1130, which  is  a
          re-badged LEO FS-1130 scanner. See sane-leo(5) for details.
 
        lexmark
-         This backend supports the Lexmark X1100 series of USB  scanners.  See
+         This  backend  supports the Lexmark X1100 series of USB scanners. See
          sane-lexmark(5) for details.
 
        ma1509
-         The  ma1509  backend  supports  the  Mustek BearPaw 1200F USB flatbed
+         The ma1509 backend supports the  Mustek  BearPaw  1200F  USB  flatbed
          scanner. See sane-ma1509(5) for details.
 
        matsushita
-         This backend supports some Panasonic KVSS high  speed  scanners.  See
+         This  backend  supports  some Panasonic KVSS high speed scanners. See
          sane-matsushita(5) for details.
 
        microtek
-         The  microtek  backend  provides  access  to  the "second generation"
-         Microtek scanners with SCSI-1 command set. See  sane-microtek(5)  for
+         The microtek backend  provides  access  to  the  "second  generation"
+         Microtek  scanners  with SCSI-1 command set. See sane-microtek(5) for
          details.
 
        microtek2
-         The  microtek2 backend provides access to some Microtek scanners with
+         The microtek2 backend provides access to some Microtek scanners  with
          a SCSI-2 command set. See sane-microtek2(5) for details.
 
        mustek
-         The SANE mustek backend supports most Mustek  SCSI  flatbed  scanners
+         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  sane-
-         mustek(5) for details.
+         II  EP  (non-SCSI).  Some  Trust  scanners  are  also  supported. See
+         sane-mustek(5) for details.
 
        mustek_pp
          The mustek_pp backend provides access to Mustek parallel port flatbed
@@ -289,108 +290,108 @@
          flatbed scanners. See sane-mustek_usb(5) for details.
 
        mustek_usb2
-         The  mustek_usb2  backend provides access to scanners using the SQ113
-         chipset like the Mustek BearPaw 2448 TA Pro USB flatbed scanner.  See
+         The mustek_usb2 backend provides access to scanners using  the  SQ113
+         chipset  like the Mustek BearPaw 2448 TA Pro USB flatbed scanner. See
          sane-mustek_usb2(5) for details.
 
        nec
-         The  SANE  nec backend supports the NEC PC-IN500/4C SCSI scanner. See
+         The SANE nec backend supports the NEC PC-IN500/4C SCSI  scanner.  See
          sane-nec(5) for details.
 
        niash
          The niash backend supports the Agfa Snapscan Touch and the HP ScanJet
-         3300c,  3400c,  and 4300c USB flatbed scanners. See sane-niash(5) for
+         3300c, 3400c, and 4300c USB flatbed scanners. See  sane-niash(5)  for
          details.
 
        pie
-         The pie backend provides access to Pacific  Image  Electronics  (PIE)
+         The  pie  backend  provides access to Pacific Image Electronics (PIE)
          and Devcom SCSI flatbed scanners. See sane-pie(5) for details.
 
        pixma
-         The  pixma  backend  supports  Canon  PIXMA MP series (multi-function
-         devices). See sane-pixma(5)  or  http://home.arcor.de/wittawat/pixma/
+         The pixma backend supports  Canon  PIXMA  MP  series  (multi-function
+         devices).  See  sane-pixma(5) or http://home.arcor.de/wittawat/pixma/
          for details.
 
        plustek
-         The  SANE  plustek backend supports USB flatbed scanners that use the
+         The SANE plustek backend supports USB flatbed scanners that  use  the
          National  Semiconductor  LM983[1/2/3]-chipset  aka  Merlin.  Scanners
          using this LM983x chips include some models from Plustek, KYE/Genius,
-         Hewlett-Packard, Mustek, Umax, Epson, and Canon. See  sane-plustek(5)
+         Hewlett-Packard,  Mustek, Umax, Epson, and Canon. See sane-plustek(5)
          for details.
 
        plustek_pp
-         The  SANE  plustek_pp  backend supports Plustek parallel port flatbed
+         The SANE plustek_pp backend supports Plustek  parallel  port  flatbed
          scanners.  Scanners using the Plustek ASIC P96001, P96003, P98001 and
-         P98003  include  some  models  from  Plustek, KYE/Genius, Primax. See
+         P98003 include some models  from  Plustek,  KYE/Genius,  Primax.  See
          sane-plustek_pp(5) for details.
 
        ricoh
-         The ricoh backend provides access  to  the  following  Ricoh  flatbed
+         The  ricoh  backend  provides  access  to the following Ricoh flatbed
          scanners: IS50 and IS60. See sane-ricoh(5) for details.
 
        s9036
-         The  s9036  backend provides access to Siemens 9036 flatbed scanners.
+         The s9036 backend provides access to Siemens 9036  flatbed  scanners.
          See sane-s9036(5) for details.
 
        sceptre
-         The sceptre backend provides access  to  the  Sceptre  S1200  flatbed
+         The  sceptre  backend  provides  access  to the Sceptre S1200 flatbed
          scanner. See sane-sceptre(5) for details.
 
        sharp
-         The  SANE  sharp  backend  supports  Sharp  SCSI  scanners. See sane-
-         sharp(5) for details.
+         The  SANE  sharp  backend   supports   Sharp   SCSI   scanners.   See
+         sane-sharp(5) for details.
 
        sm3600
-         The SANE sm3600 backend supports  the  Microtek  ScanMaker  3600  USB
+         The  SANE  sm3600  backend  supports  the Microtek ScanMaker 3600 USB
          scanner. See sane-sm3600(5) for details.
 
        sm3840
-         The  SANE  sm3840  backend  supports  the Microtek ScanMaker 3840 USB
+         The SANE sm3840 backend supports  the  Microtek  ScanMaker  3840  USB
          scanner.  See sane-sm3840(5) for details.
 
        snapscan
-         The snapscan backend supports AGFA  SnapScan  flatbed  scanners.  See
+         The  snapscan  backend  supports  AGFA SnapScan flatbed scanners. See
          sane-snapscan(5) for details.
 
        sp15c
-         This  backend supports the Fujitsu FCPA ScanPartner 15C flatbed scan-
+         This backend supports the Fujitsu FCPA ScanPartner 15C flatbed  scan-
          ner. See sane-sp15c(5) for details.
 
        st400
-         The sane-st400 backend provides access to Siemens  ST400  and  ST800.
+         The  sane-st400  backend  provides access to Siemens ST400 and ST800.
          See sane-st400(5) for details.
 
        tamarack
-         The  SANE  tamarack  backend supports Tamarack Artiscan flatbed scan-
+         The SANE tamarack backend supports Tamarack  Artiscan  flatbed  scan-
          ners. See sane-tamarack(5) for details.
 
        teco1 teco2 teco3
-         The SANE teco1, teco2 and teco3 backends support some TECO  scanners,
+         The  SANE teco1, teco2 and teco3 backends support some TECO scanners,
          usually sold under the Relisys, Trust, Primax, Piotech, Dextra names.
          See sane-teco1(5), sane-teco2(5) and sane-teco3(5) for details.
 
        u12
          The sane-u12 backend provides USB flatbed scanners based on Plustek's
-         ASIC  98003  (parallel-port  ASIC)  and a GeneSys Logics' USB-parport
-         bridge chip like the Plustek OpticPro  U(T)12.  See  sane-u12(5)  for
+         ASIC 98003 (parallel-port ASIC) and  a  GeneSys  Logics'  USB-parport
+         bridge  chip  like  the  Plustek OpticPro U(T)12. See sane-u12(5) for
          details.
 
        umax
-         The  sane-umax  backend provides access to several UMAX-SCSI-scanners
+         The sane-umax backend provides access to  several  UMAX-SCSI-scanners
          and some Linotype Hell SCSI-scanners. See sane-umax(5) for details.
 
        umax_pp
-         The sane-umax_pp  backend  provides  access  to  Umax  parallel  port
+         The  sane-umax_pp  backend  provides  access  to  Umax  parallel port
          flatbed scanners and the HP 3200C. See sane-umax_pp(5) for details.
 
        umax1200u
-         The  sane-umax1220u  backend  supports  the  UMAX  Astra  1220U (USB)
-         flatbed scanner (and also the UMAX Astra 2000U, sort of).  See  sane-
-         umax1220u(5) for details.
+         The sane-umax1220u  backend  supports  the  UMAX  Astra  1220U  (USB)
+         flatbed  scanner  (and  also  the  UMAX  Astra  2000U,  sort of). See
+         sane-umax1220u(5) for details.
 
-       Also,  have  a look at the backend information page at http://www.sane-
-       project.org/sane-supported-devices.html and the  list  of  projects  in
-       /usr/doc/sane-1.0.19/PROJECTS.
+       Also,   have   a   look   at   the   backend   information   page    at
+       http://www.sane-project.org/sane-supported-devices.html and the list of
+       projects in /usr/doc/sane-1.0.20/PROJECTS.
@@ -405,14 +406,14 @@ Backend for Kodak DC20/DC25 Digital Cameras. See sane-dc25(5). dmc - Backend for the Polaroid Digital Microscope Camera. See sane-dmc(5). + Backend for the Polaroid Digital Microscope Camera. See sane-dmc(5). gphoto2 Backend for digital cameras supported by the gphoto2 library package. - (See http://www.gphoto.org for more information and a list of sup- - ported cameras.) Gphoto2 supports over 140 different camera models. - However, please note that more development and testing is needed - before all of these cameras will be supported by SANE backend. See + (See http://www.gphoto.org for more information and a list of sup- + ported cameras.) Gphoto2 supports over 140 different camera models. + However, please note that more development and testing is needed + before all of these cameras will be supported by SANE backend. See sane-gphoto2(5). qcam @@ -422,82 +423,83 @@ The sane-st680 backend provides access to webcams with a stv680 chip. See sane-st680(5) for details. - Also, have a look at the backend information page at http://www.sane- - project.org/sane-supported-devices.html and the list of projects in - /usr/doc/sane-1.0.19/PROJECTS. + Also, have a look at the backend information page at + http://www.sane-project.org/sane-supported-devices.html and the list of + projects in /usr/doc/sane-1.0.20/PROJECTS.

MISCELLANEOUS BACKENDS

        dll
-         The sane-dll library implements a SANE backend that  provides  access
+         The  sane-dll  library implements a SANE backend that provides access
          to an arbitrary number of other SANE backends by dynamic loading. See
          sane-dll(5).
 
        net
-         The SANE network daemon saned provides access to scanners located  on
-         different  computers  in  connection  with the net backend. See sane-
-         net(5) and saned(8).
+         The  SANE network daemon saned provides access to scanners located on
+         different  computers  in  connection  with  the  net   backend.   See
+         sane-net(5) and saned(8).
 
        pnm
-         PNM image reader pseudo-backend. The purpose of this backend is  pri-
+         PNM  image reader pseudo-backend. The purpose of this backend is pri-
          marily to aid in debugging of SANE frontends. See sane-pnm(5).
 
        pint
-         Backend  for  scanners  that  use the PINT (Pint Is Not Twain) device
-         driver.  The PINT driver is being actively developed on  the  OpenBSD
+         Backend for scanners that use the PINT (Pint  Is  Not  Twain)  device
+         driver.   The  PINT driver is being actively developed on the OpenBSD
          platform, and has been ported to a few other *nix-like operating sys-
          tems. See sane-pint(5).
 
        test
          The SANE test backend is for testing frontends and the SANE installa-
-         tion.   It provides test pictures and various test options. See sane-
-         test(5).
+         tion.  It provides  test  pictures  and  various  test  options.  See
+         sane-test(5).
 
        v4l
-         The sane-v4l library implements a SANE backend that provides  generic
-         access  to  video  cameras and similar equipment using the V4L (Video
+         The  sane-v4l library implements a SANE backend that provides generic
+         access to video cameras and similar equipment using  the  V4L  (Video
          for Linux) API. See sane-v4l(5).
 
-       Also, have a look at the backend information page  at  http://www.sane-
-       project.org/sane-supported-devices.html  and  the  list  of projects in
-       /usr/doc/sane-1.0.19/PROJECTS.
+       Also,    have   a   look   at   the   backend   information   page   at
+       http://www.sane-project.org/sane-supported-devices.html and the list of
+       projects in /usr/doc/sane-1.0.20/PROJECTS.

CHANGING THE TOP-LEVEL BACKEND

-       By default, all SANE backends (drivers) are loaded dynamically  by  the
-       sane-dll  meta  backend.  If  you  have any questions about the dynamic
-       loading, read sane-dll(5).  SANE frontend can also be linked  to  other
-       backends  directly  by  copying  or  linking a backend to libsane.so in
+       By  default,  all SANE backends (drivers) are loaded dynamically by the
+       sane-dll meta backend. If you have  any  questions  about  the  dynamic
+       loading,  read  sane-dll(5).  SANE frontend can also be linked to other
+       backends directly by copying or linking  a  backend  to  libsane.so  in
        /usr/lib/sane.

DEVELOPER'S DOCUMENTATION

-       It's not hard to write a SANE backend. It can take some time,  however.
-       You  should  have  basic  knowledge  of  C  and enough patience to work
+       It's  not hard to write a SANE backend. It can take some time, however.
+       You should have basic knowledge  of  C  and  enough  patience  to  work
        through the documentation and find out how your scanner works. Appended
-       is  a list of some documents that help to write backends and frontends.
+       is a list of some documents that help to write backends and  frontends.
 
-       The SANE standard defines the application programming  interface  (API)
-       that  is  used to communicate between frontends and backends. It can be
-       found at /usr/doc/sane-1.0.19/sane.ps (if latex is  installed  on  your
-       system)  and  on  the  SANE  website: http://www.sane-project.org/html/
+       The  SANE  standard defines the application programming interface (API)
+       that is used to communicate between frontends and backends. It  can  be
+       found at /usr/doc/sane-1.0.20/sane.ps (if latex is installed on your
+       system) and  on  the  SANE  website:  http://www.sane-project.org/html/
        (HTML), or http://www.sane-project.org/sane.ps (Postscript).
 
-       There    is    some    more    information    for    programmers     in
-       /usr/doc/sane-1.0.19/backend-writing.txt.   Most  of  the internal SANE
-       routines  (sanei)  are  documented  using   doxygen:   http://www.sane-
-       project.org/sanei/.   Before  a  new  backend  or  frontend  project is
-       started, have a look at /usr/doc/sane-1.0.19/PROJECTS for projects that
-       are  planned  or not yet included into the SANE distribution and at our
-       bug-tracking system:  http://www.http://www.sane-project.org/bugs.html.
+       There     is    some    more    information    for    programmers    in
+       /usr/doc/sane-1.0.20/backend-writing.txt.  Most of the internal SANE
+       routines      (sanei)      are      documented      using      doxygen:
+       http://www.sane-project.org/sanei/.  Before a new backend  or  frontend
+       project is started, have a look at /usr/doc/sane-1.0.20/PROJECTS for
+       projects that are planned or not yet included into the  SANE  distribu-
+       tion        and        at        our        bug-tracking        system:
+       http://www.http://www.sane-project.org/bugs.html.
 
-       There  are  some links on how to find out about the protocol of a scan-
+       There are some links on how to find out about the protocol of  a  scan-
        ner: http://www.meier-geinitz.de/sane/misc/develop.html.
 
-       If you start writing a backend or frontend or any other part  of  SANE,
+       If  you  start writing a backend or frontend or any other part of SANE,
        please contact the sane-devel mailing list for coordination so the same
        work isn't done twice.
 
@@ -511,135 +513,136 @@
               The static libraries implementing the backends.
 
        /usr/lib/sane/libsane-*.so
-              The shared libraries implementing the backends (present on  sys-
+              The  shared libraries implementing the backends (present on sys-
               tems that support dynamic loading).
 
-       /usr/doc/sane-1.0.19/*
-              SANE  documentation: The standard, READMEs, text files for back-
+       /usr/doc/sane-1.0.20/*
+              SANE documentation: The standard, READMEs, text files for  back-
               ends etc.

PROBLEMS

        If your device isn't found but you know that it is supported, make sure
-       that  it  is  detected by your operating system. For SCSI and USB scan-
-       ners, use the  sane-find-scanner  tool  (see  sane-find-scanner(1)  for
-       details).  It prints one line for each scanner it has detected and some
-       comments (#). If sane-find-scanner finds your scanner only as root  but
-       not  as  normal  user,  the  permissions  for  the device files are not
-       adjusted correctly. If the scanner isn't found at  all,  the  operating
+       that it is detected by your operating system. For SCSI  and  USB  scan-
+       ners,  use  the  sane-find-scanner  tool  (see sane-find-scanner(1) for
+       details). It prints one line for each scanner it has detected and  some
+       comments  (#). If sane-find-scanner finds your scanner only as root but
+       not as normal user, the  permissions  for  the  device  files  are  not
+       adjusted  correctly.  If  the scanner isn't found at all, the operating
        system hasn't detected it and may need some help. Depending on the type
        of your scanner, read sane-usb(5) or sane-scsi(5).  If your scanner (or
        other device) is not connected over the SCSI bus or USB, read the back-
        end's manual page for details on how to set it up.
 
-       Now your scanner is detected by the operating system but not  by  SANE?
-       Try  scanimage  -L.   If the scanner is not found, check that the back-
-       end's name is mentioned in  /etc/sane.d/dll.conf.   Some  backends  are
-       commented  out  by default. Remove the comment sign for your backend in
-       this case. Also some backends aren't compiled at all if  one  of  their
-       prerequisites  are  missing.  Examples  include dc210, dc240, canon_pp,
-       hpsj5s, gphoto2, pint, qcam, v4l, net, sm3600, snapscan,  pnm.  If  you
-       need  one  of  these backends and they aren't available, read the build
-       instructions in the README file and the individual manual pages of  the
+       Now  your  scanner is detected by the operating system but not by SANE?
+       Try scanimage -L.  If the scanner is not found, check  that  the  back-
+       end's  name  is  mentioned  in /etc/sane.d/dll.conf.  Some backends are
+       commented out by default. Remove the comment sign for your  backend  in
+       this  case.  Also  some backends aren't compiled at all if one of their
+       prerequisites are missing. Examples  include  dc210,  dc240,  canon_pp,
+       hpsj5s,  gphoto2,  pint,  qcam, v4l, net, sm3600, snapscan, pnm. If you
+       need one of these backends and they aren't available,  read  the  build
+       instructions  in the README file and the individual manual pages of the
        backends.
 
-       Another  reason for not being detected by scanimage -L may be a missing
-       or wrong configuration in the backend's configuration file. While  SANE
-       tries  to  automatically  find  most scanners, some can't be setup cor-
-       rectly without the intervention of  the  administrator.  Also  on  some
+       Another reason for not being detected by scanimage -L may be a  missing
+       or  wrong configuration in the backend's configuration file. While SANE
+       tries to automatically find most scanners, some  can't  be  setup  cor-
+       rectly  without  the  intervention  of  the administrator. Also on some
        operating systems auto-detection may not work. Check the backend's man-
        ual page for details.
 
        If your scanner is still not found, try setting the various environment
-       variables  that  are available to assist in debugging.  The environment
+       variables that are available to assist in debugging.   The  environment
        variables are documented in the relevant manual pages.  For example, to
-       get  the maximum amount of debug information when testing a Mustek SCSI
-       scanner, set environment variables  SANE_DEBUG_DLL,  SANE_DEBUG_MUSTEK,
-       and  SANE_DEBUG_SANEI_SCSI  to  128 and then invoke scanimage -L .  The
+       get the maximum amount of debug information when testing a Mustek  SCSI
+       scanner,  set  environment variables SANE_DEBUG_DLL, SANE_DEBUG_MUSTEK,
+       and SANE_DEBUG_SANEI_SCSI to 128 and then invoke scanimage  -L  .   The
        debug messages for the dll backend tell if the mustek backend was found
-       and  loaded at all. The mustek messages explain what the mustek backend
-       is doing while the SCSI debugging shows the low level handling. If  you
+       and loaded at all. The mustek messages explain what the mustek  backend
+       is  doing while the SCSI debugging shows the low level handling. If you
        can't find out what's going on by checking the messages carefully, con-
        tact the sane-devel mailing list for help (see REPORTING BUGS below).
 
        Now that your scanner is found by scanimage -L, try to do a scan: scan-
-       image  >image.pnm.   This command starts a scan for the default scanner
-       with default settings. All the available options are listed by  running
-       scanimage  --help.   If  scanning aborts with an error message, turn on
-       debugging as mentioned above. Maybe the configuration file  needs  some
-       tuning,  e.g.  to  setup  the path to a firmware that is needed by some
-       scanners. See the backend's manual page for details. If you can't  find
+       image >image.pnm.  This command starts a scan for the  default  scanner
+       with  default settings. All the available options are listed by running
+       scanimage --help.  If scanning aborts with an error  message,  turn  on
+       debugging  as  mentioned above. Maybe the configuration file needs some
+       tuning, e.g. to setup the path to a firmware that  is  needed  by  some
+       scanners.  See the backend's manual page for details. If you can't find
        out what's wrong, contact sane-devel.
 
-       To  check  that  the SANE libraries are installed correctly you can use
-       the test backend, even if you  don't  have  a  scanner  or  other  SANE
+       To check that the SANE libraries are installed correctly  you  can  use
+       the  test  backend,  even  if  you  don't  have a scanner or other SANE
        device:
 
               scanimage -d test -T
 
-       You  should  get  a list of PASSed tests. You can do the same with your
+       You should get a list of PASSed tests. You can do the  same  with  your
        backend by changing "test" to your backend's name.
 
-       So now scanning with scanimage works and you want to  use  one  of  the
-       graphical  frontends  like  xsane, xscanimage, or quiteinsane but those
-       frontends don't detect  your  scanner?  One  reason  may  be  that  you
+       So  now  scanning  with  scanimage works and you want to use one of the
+       graphical frontends like xsane, xscanimage, or  quiteinsane  but  those
+       frontends  don't  detect  your  scanner?  One  reason  may  be that you
        installed two versions of SANE.  E.g. the version that was installed by
-       your distribution  in  /usr  and  one  you  installed  from  source  in
-       /usr/local/.   Make  sure  that  only one version is installed. Another
-       possible reason is, that your system's dynamic loader  can't  find  the
-       SANE  libraries.  For  Linux,  make  sure that /etc/ld.so.conf contains
-       /usr/local/lib and does not contain /usr/local/lib/sane.  See also  the
+       your  distribution  in  /usr  and  one  you  installed  from  source in
+       /usr/local/.  Make sure that only one  version  is  installed.  Another
+       possible  reason  is,  that your system's dynamic loader can't find the
+       SANE libraries. For Linux,  make  sure  that  /etc/ld.so.conf  contains
+       /usr/local/lib  and does not contain /usr/local/lib/sane.  See also the
        documentation of the frontends.

HOW CAN YOU HELP SANE

-       We  appreciate  any help we can get. Please have a look at our web page
+       We appreciate any help we can get. Please have a look at our  web  page
        about contributing to SANE: http://www.sane-project.org/contrib.html

CONTACT

-       For reporting bugs or requesting new  features,  please  use  our  bug-
-       tracking  system:  http://www.sane-project.org/bugs.html.  You can also
-       contact the author of your backend directly. Usually the email  address
-       can  be found in the /usr/doc/sane-1.0.19/AUTHORS file or the backend's
-       manpage. For general discussion about SANE, please use the SANE mailing
-       list sane-devel (see http://www.sane-project.org/mailing-lists.html for
-       details).
+       For  reporting  bugs  or  requesting  new features, please use our bug-
+       tracking system: http://www.sane-project.org/bugs.html.  You  can  also
+       contact  the author of your backend directly. Usually the email address
+       can be found in the /usr/doc/sane-1.0.20/AUTHORS file or  the  back-
+       end's  manpage.  For general discussion about SANE, please use the SANE
+       mailing   list   sane-devel   (see    http://www.sane-project.org/mail-
+       ing-lists.html for details).

SEE ALSO

-       saned(8),  sane-find-scanner(1),  scanimage(1),  sane-abaton(5),  sane-
-       agfafocus(5),   sane-apple(5),  sane-artec(5),  sane-artec_eplus48u(5),
-       sane-as6e(5),   sane-avision(5),   sane-bh(5),   sane-canon(5),   sane-
-       canon630u(5),  sane-canon_pp(5),  sane-coolscan2(5),  sane-coolscan(5),
-       sane-dc210(5), sane-dc240(5), sane-dc25(5),  sane-dll(5),  sane-dmc(5),
-       sane-epson(5), sane-fujitsu(5), sane-genesys(5), sane-gphoto2(5), sane-
-       gt68xx(5), sane-hp(5), sane-hpsj5s(5), sane-hp3500(5),  sane-hp3900(5),
-       sane-hp4200(5),  sane-hp5400(5),  sane-hpljm1005(5), sane-ibm(5), sane-
-       leo(5),  sane-lexmark(5),  sane-ma1509(5),  sane-matsushita(5),   sane-
-       microtek2(5),   sane-microtek(5),   sane-mustek(5),  sane-mustek_pp(5),
+       saned(8),     sane-find-scanner(1),    scanimage(1),    sane-abaton(5),
+       sane-agfafocus(5),            sane-apple(5),             sane-artec(5),
+       sane-artec_eplus48u(5),   sane-as6e(5),   sane-avision(5),  sane-bh(5),
+       sane-canon(5), sane-canon630u(5), sane-canon_pp(5),  sane-coolscan2(5),
+       sane-coolscan(5),     sane-dc210(5),    sane-dc240(5),    sane-dc25(5),
+       sane-dll(5),     sane-dmc(5),      sane-epson(5),      sane-fujitsu(5),
+       sane-genesys(5),     sane-gphoto2(5),    sane-gt68xx(5),    sane-hp(5),
+       sane-hpsj5s(5),   sane-hp3500(5),    sane-hp3900(5),    sane-hp4200(5),
+       sane-hp5400(5),  sane-hpljm1005(5), sane-ibm(5), sane-leo(5), sane-lex-
+       mark(5),   sane-ma1509(5),    sane-matsushita(5),    sane-microtek2(5),
+       sane-microtek(5),           sane-mustek(5),          sane-mustek_pp(5),
        sane-mustek_usb(5),  sane-mustek_usb2(5),   sane-nec(5),   sane-net(5),
        sane-niash(5),  sane-pie(5),  sane-pint(5), sane-plustek(5), sane-plus-
        tek_pp(5),  sane-pnm(5),  sane-qcam(5),  sane-ricoh(5),  sane-s9036(5),
-       sane-sceptre(5),  sane-scsi(5),  sane-sharp(5),  sane-sm3600(5),  sane-
-       sm3840(5),  sane-snapscan(5),   sane-sp15c(5),   sane-st400(5),   sane-
-       stv680(5),   sane-tamarack(5),   sane-teco1(5),   sane-teco2(5),  sane-
-       teco3(5), sane-test(5), sane-u12(5),  sane-umax1220u(5),  sane-umax(5),
-       sane-umax_pp(5), sane-usb(5), sane-v4l(5)
+       sane-sceptre(5),     sane-scsi(5),    sane-sharp(5),    sane-sm3600(5),
+       sane-sm3840(5),   sane-snapscan(5),    sane-sp15c(5),    sane-st400(5),
+       sane-stv680(5),    sane-tamarack(5),    sane-teco1(5),   sane-teco2(5),
+       sane-teco3(5),    sane-test(5),     sane-u12(5),     sane-umax1220u(5),
+       sane-umax(5), sane-umax_pp(5), sane-usb(5), sane-v4l(5)

AUTHOR

        David      Mosberger-Tang      and      many     many     more     (see
-       /usr/doc/sane-1.0.19/AUTHORS for details).  This man page  was  written
-       by  Henning  Meier-Geinitz. Quite a lot of text was taken from the SANE
-       standard, several man pages, and README files.
+       /usr/doc/sane-1.0.20/AUTHORS for details).  This man page was  writ-
+       ten  by  Henning  Meier-Geinitz. Quite a lot of text was taken from the
+       SANE standard, several man pages, and README files.
 
-sane-backends 1.0.19            16 October 2005                        sane(7)
+                                  14 Jul 2008                          sane(7)
diff --git a/man/saned.1.html b/man/saned.1.html deleted file mode 100644 index 4d1c72a4..00000000 --- a/man/saned.1.html +++ /dev/null @@ -1,186 +0,0 @@ - - -saned.1 - -

-

saned.1

-
-
-
-saned(1)                 SANE Scanner Access Now Easy                 saned(1)
-
-
-
-

NAME

-       saned - SANE network daemon
-
-
-
-

SYNOPSIS

-       saned [-d|-s [n]]
-
-
-
-

DESCRIPTION

-       saned  is  the SANE (Scanner Access Now Easy) daemon that allows remote
-       clients to access image acquisition  devices  available  on  the  local
-       host.
-
-
-
-

OPTIONS

-       The -d and -s flags request that saned run in debug mode (as opposed to
-       inetd(8) mode).  In this mode, saned 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., -d128 will request printing of
-       all debug info. Debug level 0 means no debug output at all. The default
-       value  is  2. If flag -d is used, the debug messages will be printed to
-       stderr while -s requests using syslog.
-
-       If saned is run from inetd or xinetd, no option can be given.
-
-
-
-

CONFIGURATION

-       First and foremost: saned 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  saned's  own
-       authentification. Don't run saned as root if it's not necessary. And do
-       not install saned as setuid root.
-
-       The contents of the saned.conf  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 saned to work properly, it is also necessary to add a configuration
-       line to /etc/inetd.conf.  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 tcpd(8) for additional security screening,
-       you may want to disable  saned  access  control  by  putting  ``+''  in
-       saned.conf  and  use  a  line  of the following form in /etc/inetd.conf
-       instead:
-
-              sane    stream    tcp    nowait    saned.saned    /usr/sbin/tcpd
-              /usr/local/sbin/saned
-
-       Note  that both examples assume that there is a saned group and a saned
-       user.  If you follow this example, please make  sure  that  the  access
-       permissions  on  the  special device are set such that saned 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
-       /etc/services:
-
-              sane 6566/tcp # SANE network scanner daemon
-
-
-
-

RESTRICTIONS

-       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 > 1024 are
-       open on the server for connections from the client.
-
-
-
-

FILES

-       /etc/hosts.equiv
-              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.
-
-       /usr/local/etc/sane.d/saned.conf
-              Contains a list of hosts permitted to access local SANE  devices
-              (see also description of SANE_CONFIG_DIR below).
-
-       /usr/local/etc/sane.d/saned.users
-              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.
-
-
-
-

ENVIRONMENT

-       SANE_CONFIG_DIR
-              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  SANE_CONFIG_DIR  to  "/tmp/config:"
-              would    result    in   directories   "tmp/config",   ".",   and
-              "/usr/local/etc/sane.d" being searched (in this order).
-
-
-
-

SEE ALSO

-       sane(7),  scanimage(1),  xscanimage(1),  xcam(1),  sane-dll(5),   sane-
-       net(5), sane-"backendname"(5)
-       http://www.penguin-breeder.org/?page=sane-net
-
-
-
-

AUTHOR

-       David Mosberger
-
-sane-backends 1.0.14-cvs          29 Oct 2003                         saned(1)
-
-
-
-Man(1) output converted with -man2html -
- - diff --git a/man/saned.8.html b/man/saned.8.html index 7981d4b2..3b355387 100644 --- a/man/saned.8.html +++ b/man/saned.8.html @@ -17,7 +17,7 @@

SYNOPSIS

-       saned [-d|-s [n]]
+       saned [ -a [ username ] | -d [ n ] | -s [ n ] ]
@@ -29,13 +29,19 @@

OPTIONS

+       The  -a flag requests that saned run in standalone daemon mode. In this
+       mode, saned will detach from the console and  run  in  the  background,
+       listening  for  incoming  client connections; inetd is not required for
+       saned operations in this mode. If the optional username is given  after
+       -a  , saned will drop root privileges and run as this user (and group).
+
        The -d and -s flags request that saned run in debug mode (as opposed to
-       inetd(8) mode).  In this mode, saned explicitly waits for a  connection
+       inetd(8)  mode).  In this mode, saned 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., -d128 will request printing of
+       lowed  by  a  number  to request debug info. The larger the number, the
+       more verbose the debug output.  E.g., -d128 will  request  printing  of
        all debug info. Debug level 0 means no debug output at all. The default
-       value  is  2. If flag -d is used, the debug messages will be printed to
+       value is 2. If flag -d is used, the debug messages will be  printed  to
        stderr while -s requests using syslog.
 
        If saned is run from inetd or xinetd, no option can be given.
@@ -45,21 +51,36 @@
 
CONFIGURATION
        First and foremost: saned 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  saned's  own
-       authentification. Don't run saned as root if it's not necessary. And do
+       wrappers  and/or  a  firewall  setup.  Don't depend only on saned's own
+       authentication. Don't run saned as root if it's not necessary.  And  do
        not install saned as setuid root.
 
-       The contents of the saned.conf  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  saned.conf configuration file contains both options for the daemon
+       and the access list.
 
+       data_portrange = min_port - max_port
+              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 saned server is sitting behind a firewall. If that firewall
+              is a Linux machine, we strongly recommend  using  the  Netfilter
+              nf_conntrack_sane 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,30 +91,34 @@
        The  case of the host names does not matter, so AHost.COM is considered
        identical to ahost.com.
 
-       For saned to work properly, it is also necessary to add a configuration
-       line to /etc/inetd.conf.  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.
+
+

+
INETD CONFIGURATION
+       For saned to work properly in its default mode of operation, it is also
+       necessary  to  add  a configuration line to /etc/inetd.conf.  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:
 
               sane-port stream tcp nowait saned.saned /usr/sbin/saned saned
 
        However, if your system uses tcpd(8) for additional security screening,
-       you may want to disable  saned  access  control  by  putting  ''+''  in
-       saned.conf  and  use  a  line  of the following form in /etc/inetd.conf
+       you  may  want  to  disable  saned  access  control by putting ''+'' in
+       saned.conf and use a line of  the  following  form  in  /etc/inetd.conf
        instead:
 
               sane-port   stream   tcp   nowait   saned.saned   /usr/sbin/tcpd
               /usr/sbin/saned
 
-       Note  that both examples assume that there is a saned group and a saned
-       user.  If you follow this example, please make  sure  that  the  access
-       permissions  on  the  special device are set such that saned can access
+       Note that both examples assume that there is a saned group and a  saned
+       user.   If  you  follow  this example, please make sure that the access
+       permissions on the special device are set such that  saned  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
+       If xinetd is installed on your system instead of  inetd  the  following
        example for xinetd.conf may be helpful:
 
               # default: off
@@ -110,25 +135,15 @@
                  server      = /usr/sbin/saned
               }
 
-       Finally, it is also necessary to add a line of the  following  form  to
+       Finally,  it  is  also necessary to add a line of the following form to
        /etc/services:
 
               sane-port 6566/tcp # SANE network scanner daemon
 
-       The  official  IANA  short name for port 6566 is "sane-port". The older
+       The official IANA short name for port 6566 is  "sane-port".  The  older
        name "sane" is now deprecated.
 
 
-

-
RESTRICTIONS
-       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  >  1024  are
-       open on the server for connections from the client.
-
-
 

 
FILES
        /etc/hosts.equiv
@@ -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.
 
 
 

@@ -169,8 +184,8 @@

SEE ALSO

-       sane(7),   scanimage(1),  xscanimage(1),  xcam(1),  sane-dll(5),  sane-
-       net(5), sane-"backendname"(5)
+       sane(7),    scanimage(1),    xscanimage(1),    xcam(1),    sane-dll(5),
+       sane-net(5), sane-"backendname"(5)
        http://www.penguin-breeder.org/?page=sane-net
 
 
@@ -178,7 +193,7 @@
 
AUTHOR
        David Mosberger
 
-sane-backends 1.0.19              30 May 2004                         saned(8)
+                                  20 Apr 2009                         saned(8)
 

 

 

diff --git a/sane-frontends.html b/sane-frontends.html
index db442bf0..68a67903 100644
--- a/sane-frontends.html
+++ b/sane-frontends.html
@@ -156,7 +156,7 @@
 	sane-frontends).  Unlike xscanimage it acquires images continuously.
       
       
  • 
-	Image Scan! for Linux
+	Image Scan! for Linux
 	- graphical frontend for Epson scanners
       
    •