Hi,
On Fri, Jun 21, 2002 at 05:02:40PM -0500, Frank Zago wrote:
> Is there a good reason to have this in the configuration files,
> alongside with /dev/scanner?
Yes :-)
> Couldn't the code in sane-find-scanner be reused in the backends?
> eg:
> sanei_find_scanner(attach_one);
You mean sanei_
--/04w6evG8XlLl3ft
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
I don't know if there is a good reason for it, but I added
/dev/usb/scanner0 to the epson.conf file. The old line is still
in there, and both usb device file entrie
Henning Meier-Geinitz wrote:
> Hi,
>
> On Fri, Jun 21, 2002 at 11:29:17AM +0100, Tim Waugh wrote:
>
>>Is there any good reason not to use (for example) '/dev/usb/scanner0'
>>instead of '/dev/usbscanner0' in the various SANE .conf files?
>
>
> Usage seems to vary between distributions, at least
Hi,
On Fri, Jun 21, 2002 at 11:29:17AM +0100, Tim Waugh wrote:
> Is there any good reason not to use (for example) '/dev/usb/scanner0'
> instead of '/dev/usbscanner0' in the various SANE .conf files?
Usage seems to vary between distributions, at least when I started
writing sane_usb, users used
--lVyydWNEvA8xBB0C
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Is there any good reason not to use (for example) '/dev/usb/scanner0'
instead of '/dev/usbscanner0' in the various SANE .conf files?
Tim.
*/
--lVyydWNEvA8xBB0C
Content-Type: application/pgp-signature
Conten
