From: Barry Schwartz <chemoelectric@chemoelectric.org>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: USB Scanner Problems with Newer Kernels/Libusb
Date: Sat, 9 Nov 2013 14:40:21 -0600 [thread overview]
Message-ID: <20131109204021.GA28493@crud> (raw)
In-Reply-To: <20131109114529.f29b71e10f00f6a8b170d0e8@comcast.net>
Frank Peters <frank.peters@comcast.net> skribis:
> Of course I could always jump on the udev bandwagon, like most everyone
> else, but I still very much enjoy the ability to control, in a simple
> manner, the operation of my own system. I don't like the idea of another
> system daemon doing things without my knowledge or approval.
I don’t blame you, because it is quite a disaster, and is becoming all
rolled up in the attempt to turn ‘Linux’ from a kernel into a
‘vertically integrated’ variant of MacOS. I’m actually using eudev,
myself, but, regardless, never know when an update will render things
like scanners non-working or at least give them incorrect access
controls.
I suppose it should be _possible_ to create the devices but would not
be surprised if the task is non-trivial. Which is very, very un-Unix,
and I think that really ought to be the end of it. I don’t mind fancy
stuff but do mind when it is done in an extremely un-Unixy fashion.
next prev parent reply other threads:[~2013-11-09 20:40 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 [this message]
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
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=20131109204021.GA28493@crud \
--to=chemoelectric@chemoelectric.org \
--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