Re: Re: pattern matching in udev

Re: Re: pattern matching in udev

[Stephane Chauveau]

> > REGEXP "<$bus><$vendor><$id>"="<scsi><ImageMate.*><.*:0:0:\(.*\)>",
> >              NAME="mem\1-%n"
>
> IMO the pattern matching should be part of the TOPOLOGY plus PLACE. 
>
> The scsi naming also requires a parent, your example above is only valid
> if you have one host adapter connected (or one usb mass storage device
> attached), there could exist another sd on *:0:0:0.

Not really because my example matches the $bus, the $id and the $vendor.
A single method capable of pattern matching on all the available informations 
could be used to replace all the methods currently in implemented in udev 
(except maybe REPLACE which has a different purpose). 

Stephane.







-------------------------------------------------------
This SF.net email is sponsored by OSDN's Audience Survey.
Help shape OSDN's sites and tell us what you think. Take this
five minute survey and you could win a $250 Gift Certificate.
http://www.wrgsurveys.com/2003/osdntech03.php?site=8
_______________________________________________
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

Re: Re: pattern matching in udev

[Patrick Mansfield]

On Wed, Dec 03, 2003 at 08:19:44PM +0100, Stephane Chauveau wrote:
> > > REGEXP "<$bus><$vendor><$id>"="<scsi><ImageMate.*><.*:0:0:\(.*\)>",
> > >              NAME="mem\1-%n"
> >
> > IMO the pattern matching should be part of the TOPOLOGY plus PLACE. 
> >
> > The scsi naming also requires a parent, your example above is only valid
> > if you have one host adapter connected (or one usb mass storage device
> > attached), there could exist another sd on *:0:0:0.
> 
> Not really because my example matches the $bus, the $id and the $vendor.

There could be another identical scsi device with the same id and vendor.

I thought the PCI sysfs id's were constant for a given hardware, but I'm
told they can change with PCI hotplug, so the full sysfs path I mentioned
previously will not be constant across boots with PCI hotplugging.

> A single method capable of pattern matching on all the available informations 
> could be used to replace all the methods currently in implemented in udev 
> (except maybe REPLACE which has a different purpose). 

-- Patrick Mansfield


-------------------------------------------------------
This SF.net email is sponsored by OSDN's Audience Survey.
Help shape OSDN's sites and tell us what you think. Take this
five minute survey and you could win a $250 Gift Certificate.
http://www.wrgsurveys.com/2003/osdntech03.php?site=8
_______________________________________________
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