From: Frank Peters <frank.peters@comcast.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: USB Scanner Problems with Newer Kernels/Libusb [Solved]
Date: Mon, 11 Nov 2013 19:03:18 -0500 [thread overview]
Message-ID: <20131111190318.98783dd7a5ff67aab23c53e5@comcast.net> (raw)
In-Reply-To: <20131110015302.GA6695@crud>
On Sat, 9 Nov 2013 19:53:02 -0600
Barry Schwartz <chemoelectric@chemoelectric.org> wrote:
>
> It is nice to know how to dump e?udev, just in case; and I also use a scanner.
>
I just want to add a parting shot to this thread.
I have several scanners and laser printers, all USB, that have not
been supported under Microsoft Windows for some time. No MS drivers are
available for these devices. On various MS Windows forums many people
ask in vain about obtaining such drivers.
But under Linux all my scanners and printers continue to work without problem,
and most likely will continue to work for many years to come.
This just underscores the difference between proprietary and open source
software.
Frank Peters
next prev parent reply other threads:[~2013-11-12 0:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-09 3:25 [gentoo-amd64] USB Scanner Problems with Newer Kernels/Libusb Frank Peters
2013-11-09 12:29 ` [gentoo-amd64] " Duncan
2013-11-09 16:45 ` Frank Peters
2013-11-09 20:40 ` Barry Schwartz
2013-11-09 21:38 ` Frank Peters
2013-11-09 22:11 ` Barry Schwartz
2013-11-09 22:57 ` Mark Knecht
2013-11-09 23:10 ` Barry Schwartz
2013-11-10 16:54 ` Tanstaafl
2013-11-10 17:08 ` Barry Schwartz
2013-11-09 23:25 ` Frank Peters
2013-11-09 23:57 ` Barry Schwartz
2013-11-10 1:30 ` [gentoo-amd64] Re: USB Scanner Problems with Newer Kernels/Libusb [Solved] Frank Peters
2013-11-10 1:53 ` Barry Schwartz
2013-11-10 2:36 ` Frank Peters
2013-11-10 4:26 ` Frank Peters
2013-11-12 0:03 ` Frank Peters [this message]
2013-11-12 23:18 ` [gentoo-amd64] " Jörg Schaible
2013-11-13 9:14 ` Paul Jewell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131111190318.98783dd7a5ff67aab23c53e5@comcast.net \
--to=frank.peters@comcast.net \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox