> From: Andrei Borzenkov
>
> Please copy-paste actual command invocation and its output.
No need. I had used = instead of == on the DRIVERS. Works fine now. Thanks for
your assistance.
--
Ciao, Paul D. DeRocco
Paulmailto:pdero...@ix.netcom.com
__
12.07.2017 02:53, Paul D. DeRocco пишет:
>> From: Andrei Borzenkov [mailto:arvidj...@gmail.com]
>>
>>> KERNEL=="midiC*", DRIVERS=="snd-usb-audio", SYMLINK+="midi%k"
>>
>> You probably want %b instead of %k here which should refer to device
>> name matched by DRIVERS.
>>
>> Start with "udevadm test
> From: Andrei Borzenkov [mailto:arvidj...@gmail.com]
>
> > KERNEL=="midiC*", DRIVERS=="snd-usb-audio", SYMLINK+="midi%k"
>
> You probably want %b instead of %k here which should refer to device
> name matched by DRIVERS.
>
> Start with "udevadm test" to verify.
I tried the following rule:
AC
> From: Andrei Borzenkov [mailto:arvidj...@gmail.com]
>
> > There is already a symlink
> > "/dev/snd/by-path/platform-3f98.usb-usb-0:1.2:1.0", but
> > it refers to
> > the useless "controlC1" interface. It also doesn't appear
> > to be generated
> > by an explicit rule anywhere that might s
11.07.2017 05:33, Paul D. DeRocco пишет:
> That is, I want a rule for creating a symlink that describes the USB port
> something is plugged into, rather than the specific device plugged into
> it. Linux USB has a way of representing the location of each physical
> jack, even when hubs are involved.
That is, I want a rule for creating a symlink that describes the USB port
something is plugged into, rather than the specific device plugged into
it. Linux USB has a way of representing the location of each physical
jack, even when hubs are involved. For devices like USB serial and USB
MIDI, I'd li
