Dr. Canek Peláez Valdés: ... > Where do you get that impression from? The OP needs handling keyboard and > mouse (as per his first email), and to do that in Linux these days, you > basically need udev, because xf86-input-mouse and xf86-input-keyboard are > going the way of the dodo.
It is inconvenient that thoose two goes away. Regarding udev, it has never supported serial mice, so it doesn't help me. ... > My point is that it's not his call; it's the call of the developers of the > software that he decided to use. 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. > > Yes I take your point, but bloat is bloat, and bloat is a liability. > > > > There is no bloat; the developers *need* to handle the dynamic hardware > case *and* the static hardware case. With udev, they handle both; otherwise > there would be two code routes: one for static and another for dynamic > hardware. ... 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. Udev is just something pushed on me for no gain except possible to satisfy some dependancy touted to be beneficial. So in this very specific case it can be considered "bloat" if you wish to use that kind of words. My guess is that it is more useful on laptop than on a desktop box or an industrial computer. /// As a side note, from what I understand, udev today is mostly about usb-devices because that is where the dynamic hardware comes from today (at least when we are not talking about hotplugging cpus, memory cards, io-cards and such (but that is more of a enterprise problem than a small system problem. Serial ports are darn easy to implement in hardware and softwere. E.g. if I have a program connecting to a device using a serial and it is disconnected, I can just reconnect it and nothing special happens, noting to be done in software except logging. The same device via usb, the dis-/reconnect will close the port and make it vanish forcing med to find out find out where the new /dev file is and reopen and reinitialize it. In hardware, mcu's without usb are cheap and their serial port are simpe to program and the serial port "stack" is vanishingly small. Just look at the tty_* files in http://aspodata.se/git/openhw/libarm/ http://aspodata.se/git/openhw/libarm/stm32/ For usb support, I need an usb stack (which is larger), e.g. https://github.com/libopencm3/libopencm3/tree/master/lib/usb I need to understand the usb protocol and all thoose structs to fill in, and in the end I get a system that is harder to program on the host side for no gain other than that +5V is provided by usb. Regards, /Karl Hammar
