Dr. Canek Peláez Valdés: > On Mon, Aug 23, 2021 at 11:07 AM <k...@aspodata.se> wrote: ... > > Regarding udev, it has never > > supported serial mice, so it doesn't help me. > What are you talking about? Udev doesn't "support" any hardware; as the > manual page states[1], it: "supplies the system software with device > events, manages permissions of device nodes and may create additional > symlinks in the /dev/ directory, or renames network interfaces".
Why would I need such a thing, I don't need any changes to /dev. Even if I pop in a usb-disk, I just mount it. Udev do not in the slightest solve any of my needs. So why are you telling me that I must have it, yes, software dependancies are a problem. I'm interested in answers that tells me how to solve that without calling in extra software and deamons. > If the kernel supports the hardware, udev will supply the corresponding > event, so udev will generate the corresponding event for serial mice also > (probably close to boot time). You can try gpm to do that. Udev do not do any way of serial mouce detection, never has. > > Poeple write whatever software they want to or are paid to do. It is my > > call if I want to use that software or not. > Well, yeah; but if you want to use software X, and X depends on Y, then you > either use software Y or don't use software X. The dependency chain can and > will grow depending on several factors, and it's the situation here if I'm > not mistaken: you want to keep using keyboard and mice, those depend on > libinput, and libinput depends on udev. I'm not a passive consumer in this as you seem to believe. If I decide I will resurrect thoose x11 drivers, I will do so. ... > > As I wrote before, udev does not handle serial mice, so udev does not > > solve anything for me nor does it help me in any way to run my systems. > You are saying it wrong, you mean to say: "to handle serial mice, I don't > need udev". And that is 100% completely true; you can keep a static /dev, > don't use udev and create the device nodes by hand. But serial mice > work great under udev also. Yea, it does, simply because udev doesn't touch any serial mouse, you have to fill in your own xorg.conf section for that or use gpm in a console. Udev just cares about the serial port, not what is attached to that port > It's not only USB; it's Bluetooth, Thunderbolt, eSATA and eSATAp, etc. The > computing world is dominated by dynamic hardware; it has been so for at > least the last two decades. Bluetooth adapters mostly comes in as a usb device, thought there might be thoose with an i2c connection for the embedded market. I don't know about thunderbolt. esata as well as sata just works well without udev. And I do not need a deamon to handle that. > > Serial ports are darn easy to implement in hardware and softwere. .. > Yes: but the software that *uses* mice doesn't care *ONLY* about serial > port mice. They care about USB mice (which is the majority) and Bluetooth > mice (which has the second place). Right now, serial mice have to be a > distant third place, if at all. Well, "if at all", so you agree with me that udev isn't for me. What I'm looking for is alternatives. > So the developers of software that deals with mice don't need to worry > *ONLY* about your case; they need to worry about the general case. Which > includes USB and Bluetooth (and whatever they invent in the future). So, udev isn't for me, what do you complain about. I don't say to others to not use udev, I don't care about that. I ask, how can I make my case work without udev, because honsestly, it doesn't bring me shit and I'm not interesed in using software that doesn't do anything for me. The problem of device nodes and permission is already solved, I don't need pop-ups, I don't want automounting. Serial ports have been working for the last 70 years or more. So stop this, I never asked about udev or how to make that work. You are answering the wrong question. Regards, /Karl Hammar
