[sane-devel] GUI for sane configuration

[Henning Meier-Geinitz]

Hi,

On Thu, Apr 18, 2002 at 01:04:41AM +0200, Christian Fughe wrote:
> My suggestions:
> 
> 1.) After several successful years of sane it is up to the time ( Die Zeit
>     is reif :-) ) to make sane an official member of /etc/services and
>     /etc/inetd.conf. I use SuSE 7.1.

I'm really surprised that it isn't at least in /etc/services.

One could argue that adding saned to inetd.conf by default is a
security risk. I wouln't install it if I hadn't a scanner that should
be shared. But I would at least ask the user if he would like to use
saned when installing the SuSE SANE package.

>     Perhaps this suggestion became
>     already standard for other distributions. Maybe, the SuSE setup tool
>     does not support saned, because saned is not an official member (man
>     saned) of these /etc/* files. Maybe, an authorized sane-member should
>     ask SuSE to add support for saned. They do advertise with sane scanner
>     support.

I haven't used SuSE for years now, so I guess I'm not the right one to
ask.

> 2.) Give the net-backend and saned a chance to be operative after 'make
>     install'.

I'm nitpicking here, but it does work out-of-the-box. You don't need
to edit the configuration file, you can just do e.g.

scanimage -d net:some.remote.server:mustek:/dev/scanner --help

or even only

scanimage -d net:some.remote.server --help

The list in net.conf is only necessary if you don't want to add the
host name with every scan command and to allow listing all scanners on
all remote servers.

Bye,
  Henning