From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Does sysfs really provides persistent hardware path to devices?
Date: Sat, 26 Jul 2003 09:43:17 -0700 [thread overview]
Message-ID: <20030726094317.7976a350.rddunlap@osdl.org> (raw)
In-Reply-To: <200307262036.13989.arvidjaar@mail.ru>
On Sat, 26 Jul 2003 20:36:13 +0400 Andrey Borzenkov <arvidjaar@mail.ru> wrote:
|
| As far as I can tell sysfs device names include logical bus numbers which
| means, if hardware is added or removed it is possible names do change.
|
| Example:
|
| /sys/devices/pci0000:00/0000:00:1f.4/usb2/2-2/2-2.1/2-2.1:0/host1/1:0:0:0
|
| PCI part reflects bus number. Now this example is trivial in that it is
| integrated USB controller so it is unlikely to ever change its number - but
| if it were external controller (and even worse with PCI-to-PCI bridge) it is
| likely that adding extra card would shift all numbers.
|
| And USB part of name starts with logical USB bus number i.e. it is obvious
| that adding one more USB adapter will definitely change it.
|
| So apparently I cannot rely on sysfs to get reliable persistent information
| about physical location of devices.
|
| the point is - I want to create aliases that would point to specific slots.
| I.e. when I plug USB memory stick in upper slot on front panel I'd like to
| always create the same device alias for it.
You'll probably get a barrage of replies...
You want udev + namedev, userspace naming policy. See the recent
udev announcements from Greg Kroah-Hartman.
udev/namedev use sysfs device tree info to apply device naming policy.
>From Greg's version 0.2 announcement:
<quotes>
kernel.org/pub/linux/utils/kernel/hotplug/udev-0.2.tar.gz
There's a BitKeeper tree of the latest stuff available at:
bk://kernel.bkbits.net/gregkh/udev/
I've also placed the slides from my OLS talk up at:
http://www.kroah.com/linux/talks/ols_2003_udev_talk/
The paper which attempts to explain the background of udev, what it
does, and where it is going is at:
http://archive.linuxsymposium.org/ols2003/Proceedings/All-Reprints/Reprint-Kroah-Hartman-OLS2003.pdf
</selected quotes>
There's more in the announcment email. This is still early code,
so there's much more to be done on it, but the demo yesterday looked
very good.
--
~Randy
| http://developer.osdl.org/rddunlap/ | http://www.xenotime.net/linux/ |
For Linux-2.6:
http://www.codemonkey.org.uk/post-halloween-2.5.txt
or http://lwn.net/Articles/39901/
http://www.kernel.org/pub/linux/kernel/people/rusty/modules/
next prev parent reply other threads:[~2003-07-26 16:30 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-26 16:36 Does sysfs really provides persistent hardware path to devices? Andrey Borzenkov
2003-07-26 16:43 ` Randy.Dunlap [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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 20:34 ` Andrey Borzenkov
2004-01-17 21:34 ` Greg KH
2004-01-17 21:34 ` Greg KH
2004-01-18 1:03 ` Kay Sievers
2004-01-18 14:05 ` Kay Sievers
2004-01-19 19:51 ` Greg KH
2004-03-14 19:25 ` Horst von Brand
2004-03-14 19:25 ` Horst von Brand
2004-01-19 13:08 ` Olaf Hering
2004-01-19 13:08 ` Olaf Hering
2004-01-19 13:59 ` Andries Brouwer
2004-01-19 13:59 ` Andries Brouwer
2004-01-19 14:04 ` Olaf Hering
2004-01-19 14:04 ` Olaf Hering
2004-03-14 11:53 ` Andrey Borzenkov
2004-03-14 11:53 ` Andrey Borzenkov
2003-08-19 17:56 David Brownell
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=20030726094317.7976a350.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=arvidjaar@mail.ru \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.