1 |
On Sat, 9 Nov 2013 14:40:21 -0600 |
2 |
Barry Schwartz <chemoelectric@×××××××××××××.org> wrote: |
3 |
|
4 |
> |
5 |
> I suppose it should be _possible_ to create the devices but would not |
6 |
> be surprised if the task is non-trivial. |
7 |
> |
8 |
|
9 |
Right now I am investigating if I can employ the udev daemon to create |
10 |
the necessary devices, when needed, in the /dev tree. IOW, I want to find |
11 |
out if I can just start the daemon, plug in the scanner, and have udev create |
12 |
the things I need. Then, when I am done scanning, I can just shut off the |
13 |
daemon. This method should allow me to use udev (or eudev) only when |
14 |
I need to use it. Otherwise it would not be running. |
15 |
|
16 |
Hopefully, this will work. It may seem awkward, but with some custom |
17 |
scripts it should be quite painless. |
18 |
|
19 |
I can't understand why libusb will not just pull its information from |
20 |
/sys/bus/usb as a substitute for the former usbfs. |
21 |
|
22 |
> |
23 |
> because it is quite a disaster, and is becoming all |
24 |
> rolled up in the attempt to turn ‘Linux’ from a kernel into a |
25 |
> ‘vertically integrated’ variant of MacOS. |
26 |
> |
27 |
|
28 |
IMHO, those folks at freedesktop.org are going to destroy the simplicity, |
29 |
beauty, and diverse utility of Linux. |
30 |
|
31 |
I downloaded and examined sytemd to try to learn more about the udev |
32 |
process. What a convoluted mess! Compared to the simple and straightforward |
33 |
boot-up and device system which I have implemented on my machines, systemd |
34 |
is a confusing morass. For what reason? I can boot up and configure my |
35 |
entire machine using a single bash script of 155 lines (including the comments). |
36 |
Why would I want to replace that comfort and ease with the expansive cacophony |
37 |
that is systemd? |
38 |
|
39 |
The freedesktop folks can do as they please, but I will never want to |
40 |
join that party. |
41 |
|
42 |
Frank Peters |