On 07/02/2016 10:53, Daniel Golle wrote: > Hi John! > > On Sun, Feb 07, 2016 at 10:28:25AM +0100, John Crispin wrote: >> maybe i am missing the point but why would you want udev on your system >> in the first place ? > > There are situations when udev is currently the only way, such are: > * more than one 3g/wwan/usb-serial device and the need to differentiate > them based on their serial number rather than on the order the kernel > probes them. > I really like those /dev/serial/by-id/ symlinks, because they prevent > comgt to try speaking with my solar-charger and collectd from trying > to query battery-voltage and PWM currents from the 3G modem -- both > are detected as usb-serial devices, thus /dev/ttyUSB* device nodes > are created in the order they are probed -- which differs e.g. > depending on cold start or warm reset of the OS. > * similar things apply when having multiple V4L, ALSA or HID devices... > * udev rules are needed for certain USB devices to be accessible for > non-root users >
which brings us back to my second question, why not add these features to procd ? my experience is that these features can be implemented in 100 lines +/- > I agree that the both implementations (udev and eudev) are over-bloated > and I'm sure that the use-cases I'm interested in can be provided by > a few dozend lines of code and a few kilobytes in binary instead of > that 1.2M executable which includes support for all sorts of weird > legacy stuff like 3.5" floppy drivers conencted via USB... > > > Cheers > > > Daniel > _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
