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
Date: Sat, 9 Nov 2013 16:38:13 -0500 [thread overview]
Message-ID: <20131109163813.e0b90b87aefd17c03054af8c@comcast.net> (raw)
In-Reply-To: <20131109204021.GA28493@crud>
On Sat, 9 Nov 2013 14:40:21 -0600
Barry Schwartz <chemoelectric@chemoelectric.org> wrote:
>
> I suppose it should be _possible_ to create the devices but would not
> be surprised if the task is non-trivial.
>
Right now I am investigating if I can employ the udev daemon to create
the necessary devices, when needed, in the /dev tree. IOW, I want to find
out if I can just start the daemon, plug in the scanner, and have udev create
the things I need. Then, when I am done scanning, I can just shut off the
daemon. This method should allow me to use udev (or eudev) only when
I need to use it. Otherwise it would not be running.
Hopefully, this will work. It may seem awkward, but with some custom
scripts it should be quite painless.
I can't understand why libusb will not just pull its information from
/sys/bus/usb as a substitute for the former usbfs.
>
> 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.
>
IMHO, those folks at freedesktop.org are going to destroy the simplicity,
beauty, and diverse utility of Linux.
I downloaded and examined sytemd to try to learn more about the udev
process. What a convoluted mess! Compared to the simple and straightforward
boot-up and device system which I have implemented on my machines, systemd
is a confusing morass. For what reason? I can boot up and configure my
entire machine using a single bash script of 155 lines (including the comments).
Why would I want to replace that comfort and ease with the expansive cacophony
that is systemd?
The freedesktop folks can do as they please, but I will never want to
join that party.
Frank Peters
next prev parent reply other threads:[~2013-11-09 21:38 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 [this message]
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=20131109163813.e0b90b87aefd17c03054af8c@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