[mythtv-users] Udev rules get mixed-up

[Yianni]

> > SUBSYSTEM=="dvb", \
> >   ATTRS{device}=="0x8852", \
> >   ATTRS{subsystem_vendor}=="0x6981", \
> >   PROGRAM="/bin/sh -c ' K=%k; K=$${K#dvb}; N=$${K#*.}; \
> >     if [ ! -e /dev/dvb/adapter_t1/$N ] ; \
> >     then printf dvb/adapter_t1/%%s $${K#*.}; \
> >     else printf dvb/adapter_t2/%%s $${K#*.}; \
> >     fi ; \
> >     exit 0'", SYMLINK+="%c"
> 
> If I look at this rule (I made it a bit more readable) it is in
> essence 'first come first get'. The first demux to initialise gets
> placed in 'adapter_t1' the second in 'adapter_t2'. The same for the
> other devices. Obviously they initialise in parallel, creating the
> mixup.
> I assume that the distinction between dvb0 and dvb1 is made on the
> hardware order, if not, if this is also based on 'first come first
> get' there is, as I see it no way to distinguish the two adaptors.
> My next assumption is that the distinction between adaptor0 and
> adaptor1 is equal to the distinction between dvb0 and dvb1. So any
> udev-rule can not add anything in the distinction.
> 
> Tot mails,
>   Hika                            mailto:hikavdh at gmail.com

Thanks for your post, Hika

The parallel initialisation you mention really looks like the only explanation. I was hopefull, though...

To be honest, the pc is almost never off, so as long as the built-in udev rules make sure that adapter0 always points to satellite x and adapter1 to y, all is ok, even without fancy names.


Yianni
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20140917/4baaa1f6/attachment.html>