Hello, only FYI On Dec 7 10:31 Martin Wilck wrote (excerpt):
... all backends are commented out in /etc/sane.d/dll.conf by default
See sane-backends.changes that reads (excerpt): ------------------------------------------------------------------- Wed Sep 12 17:16:16 CEST 2001 - freitag@suse.de ... Disabled all dll-entries in /etc/sane.d/dll.conf to avoid probs with wrong device detection which happend in the past. The yast module enables the correct one, added a README.SuSE to the sane package doc path that describes this change. ------------------------------------------------------------------- Accordingly sane-backends.spec contains --------------------------------------------------------------------------- # Disable all backends in /etc/sane.d/dll.conf to avoid problems # when backends are active by default: perl -pi -e 's/^([^#].*)$/#$1/' %{buildroot}%{_sysconfdir}/sane.d/dll.conf --------------------------------------------------------------------------- I inherited it this way and I have zero knowledge what the actual reasoning behind was at that time. But I know there have been issues with conflicting different SANE backends for one same model. I think it could arbitrarily fail when two different SANE backends work for the same model and both backends try to communicate more or less simultaneously with the same device. This means at least one would have to ensure that it cannot happen that more than one backend is by default active for each of all the supported models. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org