sane config files [was [sane-devel] Infrared channel]]

[Johannes Meixner]

Hello,

On Feb 24 20:06 Oliver Rauch wrote (shortened):
> May be we need an additional flag to the existing ADVANCED flag, may be
> a CONFIGURE flag. This way the backend would define what the user can
> select and we already would have a configuration tool: the frontend.
> The backend could save the last selected setting in its own
> configuration file as a default option (although this also could be done
> by the frontend).

This would be great!

Please have in mind that it must be possible to seperate configuring
from daily usage.
It would lead to chaos if many different (unexperienced) users  
who may access the scanner for example via saned and net backend
can configure it as they like.

In particular it should be possible to request admin authentication
for configuring.
As an example have a look how printer configuration is done in CUPS:
Via 'lppasswd' root can permit any user to act as a CUPS admin
and in cupsd.conf admin authentication can be disabled at all.


Kind Regards
Johannes Meixner
-- 
SUSE LINUX Products GmbH, Maxfeldstrasse 5      Mail: jsmeix@suse.de
90409 Nuernberg, Germany                    WWW: http://www.suse.de/