linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ihno Krumreich <ihno@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: pattern matching in udev
Date: Thu, 04 Dec 2003 10:29:39 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-107053394916413@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-107013956514187@msgid-missing>

On Thu, Dec 04, 2003 at 10:51:32AM +0100, Olaf Hering wrote:
>  On Wed, Dec 03, Patrick Mansfield wrote:
> 
> > 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.
> 
> You cant have everything. How do you describe a filesystem to mount:
> Its either the location, then the content may change, or it is the
> content, then the location can change (content in the sense of fs UUID).
> 
> And in the case of pci cards, there is no need for PCI hotplug. Just
> open your PC and move the SCSI card from slot a to slot b. result:
> device node doesnt match if you go for location.

I think the primary goal should be that adding and removing of
devices (or controllers) does not change the name of
the old/remaning devices.
If you open the PC and redistribute the PCI-Cards to the PCI-slots
you can expect that something changed.

Ihno

-- 
Best regards/Mit freundlichen Grüßen

Ihno Krumreich

"Never trust a computer you can lift."
--
Ihno Krumreich            ihno@suse.de
SuSE Linux AG             Projectmanager S390 & zSeries
Deutschherrnstr. 15-19    +49-911-74053-439
90429 Nürnberg            http://www.suse.de


-------------------------------------------------------
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

  parent reply	other threads:[~2003-12-04 10:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-29 20:58 pattern matching in udev Stephane Chauveau
2003-12-01 16:59 ` Patrick Mansfield
2003-12-02  0:21 ` Greg KH
2003-12-04  9:51 ` Olaf Hering
2003-12-04 10:17 ` Chauveau S.
2003-12-04 10:29 ` Ihno Krumreich [this message]
2003-12-04 10:34 ` Olaf Hering

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-hotplug-107053394916413@msgid-missing \
    --to=ihno@suse.de \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).