All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dax Kelson <dax@gurulabs.com>
To: 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: 26 Jul 2003 16:51:24 -0600	[thread overview]
Message-ID: <1059259884.2924.37.camel@mentor.gurulabs.com> (raw)
In-Reply-To: <200307261259.03517.jcwren@jcwren.com>

On Sat, 2003-07-26 at 10:59, 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.

man devlabel in Red Hat Linux 9 and above would solve this 100% for you.

Also, the devlabel home page:

http://www.lerhaupt.com/linux.html

and a whitepaper on it:

http://www.dell.com/us/en/esg/topics/power_ps1q03-lerhaupt.htm


  parent reply	other threads:[~2003-07-26 22:36 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
2003-07-26 22:51   ` Dax Kelson [this message]
  -- 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=1059259884.2924.37.camel@mentor.gurulabs.com \
    --to=dax@gurulabs.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.