From: Greg KH <greg@kroah.com>
To: "J.C. Wren" <jcwren@jcwren.com>
Cc: Andrey Borzenkov <arvidjaar@mail.ru>, linux-kernel@vger.kernel.org
Subject: Re: Does sysfs really provides persistent hardware path to devices?
Date: Sat, 26 Jul 2003 13:07:14 -0400 [thread overview]
Message-ID: <20030726170714.GC3168@kroah.com> (raw)
In-Reply-To: <200307261259.03517.jcwren@jcwren.com>
On Sat, Jul 26, 2003 at 12:59:03PM -0400, J.C. Wren wrote:
> Specifically using your example of USB memories, I have seen devices move
> around just because of rebooting. I have a Sandisk SDDR-31 (MMC) and a
> SDDR-33 (CF) that remain plugged into the same USB ports all the time.
> Occasionally, they come up swapped (normally the MMC reader is /dev/sda),
> which is really infuriating, since my scripts for building MMC and CF cards
> then exhibit much breakage.
Test out udev's ability to name devices based on bus topology (the USB
bus topology doesn't change for you.) It should solve your problem.
thanks,
greg k-h
next prev parent reply other threads:[~2003-07-26 16:51 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
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 [this message]
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=20030726170714.GC3168@kroah.com \
--to=greg@kroah.com \
--cc=arvidjaar@mail.ru \
--cc=jcwren@jcwren.com \
--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.