Hi, r. a. schmied writes: > r. a. schmied wrote: >> Olaf Meeuwissen wrote: >>> [...] >>> r. a. schmied writes: >>>> [...] >>>> a query or two about <backend>.conf file >>>> >>>> 1) do all, most, some backends support such runtime argument >>>> alterations? >>> >>> Each backend basically does it own thing. There is nothing that tries >>> to impose any kind of "standard". Some backends use it to tweak their >>> device detection routines, other to set some defauls and some do a bit >>> of both. >>> >>> Your best bet is the sane-BE manual page for each BE backend. Next best >>> are the comments in the BE.conf file, if any. >>> # In the sources, you can find them as backend/BE.conf.in. >> >> [...] > > humm -- well i don't see any BE.conf (or sane-BE.man) [and did > ignore the case as well] in sane-backends-master-e13b80fa [...]
Sorry for not being clear (enough). I had hoped it was "obvious" that the BE stood for whatever backend you're interested in. We have about 94 of them in sane-backends :-) In your case, BE=genesys, that'd become sane-genesys, genesys.conf and backend/genesys.conf.in, respectively. # Perhaps I should have added a $ and write sane-$BE? Hope this helps, -- Olaf Meeuwissen, LPIC-2 FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Software https://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join -- sane-devel mailing list: [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to [email protected]
