From: Greg KH <greg@kroah.com>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Does sysfs really provides persistent hardware path to devices?
Date: Mon, 28 Jul 2003 10:03:09 -0700 [thread overview]
Message-ID: <20030728170308.GA4839@kroah.com> (raw)
In-Reply-To: <200307282044.43131.arvidjaar@mail.ru>
On Mon, Jul 28, 2003 at 08:44:43PM +0400, Andrey Borzenkov wrote:
> On Saturday 26 July 2003 20:50, Greg KH wrote:
> > On Sat, Jul 26, 2003 at 08:36:13PM +0400, Andrey Borzenkov wrote:
> > > So apparently I cannot rely on sysfs to get reliable persistent
> > > information about physical location of devices.
> >
> > That is correct, but you can get pretty close :)
> >
>
> sure, I know. The more annoying is how difficult is to step over this "close"
> :)
The kernel isn't going to do this. It's a user space issue.
> > > 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.
> >
> > Look at the udev announcement I posted to linux-kernel yesterday to see
> > how to do this.
> >
>
> I know udev.
>
> udev does not answer my question. It operates on logical device (bus) numbers.
> My question was how to name devices based on physical position
> *independently* of logical numbers they get.
You don't know udev then :)
This is exactly what udev solves. Please read the paper I posted a link
to, it should answer your questions.
> Question: how to configure udev so that "database" always refers to LUN 0 on
> target 0 on bus 0 on HBA in PCI slot 1.
If you can't rely on scsi position, then you need to look for something
that uniquely describes the device. Like a filesystem label, or a uuid
on the device. udev can handle this (well I'm still working on the
filesystem label, but others have already done the hard work for that to
be intregrated easily.)
thanks,
greg k-h
next prev parent reply other threads:[~2003-07-28 16:47 UTC|newest]
Thread overview: 23+ 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
2003-07-26 16:50 ` Greg KH
2003-07-28 16:44 ` Andrey Borzenkov
2003-07-28 17:03 ` Greg KH [this message]
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 21:34 ` Greg KH
2004-01-19 13:08 ` Olaf Hering
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
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=20030728170308.GA4839@kroah.com \
--to=greg@kroah.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox