[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: udev rules for persistent symlinks for adapter?/frontend0 devices



On 12-04-24 07:26 PM, Andy Walls wrote:
> 
> Maybe by using matches on DEVPATH and/or DEVNAME along with the other
> attributes you already check?
> 
...
> KERNEL[1335308536.258048] add      /devices/pci0000:00/0000:00:14.4/0000:03:00.0/dvb/dvb0.frontend0 (dvb)
> UDEV_LOG=3
> ACTION=add
> DEVPATH=/devices/pci0000:00/0000:00:14.4/0000:03:00.0/dvb/dvb0.frontend0

Perhaps this is the ultimate in persistence, but unfortunately is also
highly dependent on physical location in the machine (i.e. which PCI
slot even).

> SUBSYSTEM=dvb
> DEVNAME=dvb/adapter0/frontend0

AFAIU, the "adapter0" is not representative of physical device
persistence but is rather dependent on probing order.  IOW,
"dvb/adapter0/frontend0" will always be the first DVB device found but
won't be a guarantee of which physical device it is.  This is what I
currently have with /dev/dvb/adapter{0.1} which is unfortunately
unsuitable since it's so predictable.

I might end up having to bite the bullet and using DEVNAME.  :-(

Thanks for the info though, much appreciated,
b.

Attachment: signature.asc
Description: OpenPGP digital signature


[Linux Input]     [Video for Linux]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Photos]     [Yosemite Photos]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Devices]     [Yosemite Backpacking]

Add to Google Powered by Linux