Re: udev - that famouse obsolete %e option

[Kay Sievers <kay.sievers@vrfy.org>]

On Tue, 2006-08-01 at 18:17 +0200, VMiklos wrote:
> 2006/8/1, Kay Sievers <kay.sievers@vrfy.org>:
> > How would you manage the numbers to stick with a particular device
> > across reboots and reconfiguration? I can't imagine a "small tool" doing
> > that job. It is entirely device class specific how to to that, and I
> > don't think it can be solved at a generic level.
> 
> i'm thinking of cd/dvd symlinks at the moment. an example: i have a
> cdrw+dvd (hdc) drive and a dvdrw drive (sr0). using cdrom_id, it's
> possible to create the following nodes: cdrom-hdc, cdrw-hdc, dvd-hdc,
> (same for sr0) and dvdrw-sr0. then the "tool" would create
> cdrom->cdrom-hdc, cdrom1->cdrom-sr0, ..., dvdrw->dvdrw-sr0 symlinks.
> and yes, across the reboots hdc would _always_ become cdrom, and sr0
> would _always_ become cdrom1
> 
> is this a bad idea?

Yes, very bad. The kernel names hdc and sr0 are not necessarily stable,
so this does not help anything. You need to use device owned unique
properties like serial numbers, vendor/product strings, and not care
about the kernel names at all, if you want stable names.

Kay


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel