May-13th-2019, 04:23 PM
I started testing. I created the simplest udev you can think of
While I was inserting now my serial USB to RS232 converter into my netPI with this ruleset active I saw next to the standard /dev/ttyUSB0 device now also a device under /dev/usb/ttyUSB0. So it is pretty much what we want to see.
But then it came to disillution. I loaded a Raspbian Container with mapped device /dev/usb/ can guess what ... docker does not start and reports "/dev/usb: not a device node".
I searched on the internet for the reason and found the hint https://docs.docker.com/engine/reference...dline/run/ that using the --device option cannot be used for ephemeral devices. Others have that problem too. The reason is that SYMLINK creates just a symbolik link and seems not to have the same properties as the real device.
Armin
Code:
SUBSYSTEM=="tty", SYMLINK+="/usb/%k"While I was inserting now my serial USB to RS232 converter into my netPI with this ruleset active I saw next to the standard /dev/ttyUSB0 device now also a device under /dev/usb/ttyUSB0. So it is pretty much what we want to see.
But then it came to disillution. I loaded a Raspbian Container with mapped device /dev/usb/ can guess what ... docker does not start and reports "/dev/usb: not a device node".
I searched on the internet for the reason and found the hint https://docs.docker.com/engine/reference...dline/run/ that using the --device option cannot be used for ephemeral devices. Others have that problem too. The reason is that SYMLINK creates just a symbolik link and seems not to have the same properties as the real device.
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
