From: Olaf Hering <olh@suse.de>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: Greg KH <greg@kroah.com>, jw schultz <jw@pegasys.ws>,
linux-kernel@vger.kernel.org,
linux-hotplug-devel@lists.sourceforge.net
Subject: Re: Does sysfs really provides persistent hardware path to devices?
Date: Mon, 19 Jan 2004 14:08:17 +0100 [thread overview]
Message-ID: <20040119130817.GA27953@suse.de> (raw)
In-Reply-To: <200401172334.13561.arvidjaar@mail.ru>
On Sat, Jan 17, Andrey Borzenkov wrote:
> > > Well, we did not move a tiny bit since the beginning of this thread :)
> > > You still did not show me namedev configuration that implements
> > > persistent name for a device based on its physical location :)))
> >
> > Ok, do you have any other ideas of how to do this?
> >
>
> given current sysfs implementation - using wildcards remains the only
> solution. I for now am using this trivial script:
>
> pts/0}% cat /etc/udev/scripts/removables
> #!/usr/bin/perl
>
> my $devpath, $base;
>
> $base = $1 if ($ARGV[0] =~ /(.*\D)\d*$/);
> $devpath = readlink "/sys/block/$base/device";
>
> if ($devpath =~
> m|/devices/pci0000:00/0000:00:1f.4/usb2/2-2/2-2.4/2-2.4:1.0/host\d+/\d+:0:0:0|)
> {
> print "flash0";
> } elsif ($devpath =~
> m|/devices/pci0000:00/0000:00:1f.4/usb2/2-2/2-2.1/2-2.1:1.0/host\d+/\d+:0:0:0|)
> {
> print "flash1";
> } elsif ($devpath =~ m|/devices/legacy/host\d+/\d+:0:4:0|) {
> print "jaz";
> } else {
> exit(1);
> }
I'm not sure what you are trying to do. Working with the 'physical
location' of removeable devices will probably fail. The usb-storage
devices here have a serial field, I really hope it is unique, use it.
--
USB is for mice, FireWire is for men!
sUse lINUX ag, nÜRNBERG
next prev parent reply other threads:[~2004-01-19 13:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-18 6:21 "Andrey Borzenkov"
2003-08-18 20:42 ` your mail Greg KH
2003-08-31 10:54 ` Does sysfs really provides persistent hardware path to devices? Andrey Borzenkov
2003-09-24 21:18 ` Greg KH
2004-01-17 20:34 ` Andrey Borzenkov
2004-01-17 21:34 ` Greg KH
2004-01-19 13:08 ` Olaf Hering [this message]
2004-01-19 13:59 ` Andries Brouwer
2004-01-19 14:04 ` Olaf Hering
2004-03-14 11:53 ` Andrey Borzenkov
2004-03-14 19:25 ` Horst von Brand
-- strict thread matches above, loose matches on Subject: below --
2003-08-19 17:56 David Brownell
2003-07-26 16:36 Andrey Borzenkov
2003-07-26 16:43 ` Randy.Dunlap
2003-07-26 16:50 ` Greg KH
2003-07-28 16:44 ` Andrey Borzenkov
2003-07-28 17:03 ` Greg KH
2003-08-17 16:41 ` Andrey Borzenkov
2003-08-17 18:28 ` Greg KH
2003-08-18 2:04 ` jw schultz
2003-08-18 20:47 ` Greg KH
2003-07-26 16:54 ` OSDL
2003-07-26 16:59 ` J.C. Wren
2003-07-26 17:07 ` Greg KH
2003-07-26 22:51 ` Dax Kelson
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=20040119130817.GA27953@suse.de \
--to=olh@suse.de \
--cc=arvidjaar@mail.ru \
--cc=greg@kroah.com \
--cc=jw@pegasys.ws \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@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).