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 16:11:48 -0600 [thread overview]
Message-ID: <20131109221148.GA26666@crud> (raw)
In-Reply-To: <20131109163813.e0b90b87aefd17c03054af8c@comcast.net>
Frank Peters <frank.peters@comcast.net> skribis:
> 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.
Maybe you can run it once even as a non-daemon just to create the
device, similarly to running rescan-scsi-bus.
> > 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.
Yes. Particularly distressing because they are completely neglecting
GNUstep, which is an existing _thoughtful_ attempt to reconcile
Unix/GNU with an integrated desktop non-Unix folk would find familiar.
> 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?
I like baselayout but as a former Slackware user also have a strong
appreciation of a BSD-style write-a-script-for-each-runlevel. Nothing
could be simpler. I have never investigated systemd too deeply, but
simply know that I am lost trying to play with runlevels on an
Ubuntu/Debian system. (There is also the Hurd approach of not needing
such scripts in the first place, but, alas, that is not transferable
to Linux.)
next prev parent reply other threads:[~2013-11-09 22:12 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 [this message]
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=20131109221148.GA26666@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