linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: really persistent SCSI device naming
Date: Thu, 20 Nov 2003 16:54:43 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-106934858519797@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106878050616362@msgid-missing>

On Thu, Nov 13, 2003 at 10:27:17PM -0500, Martin Hicks wrote:
> 
> Hello,
> 
> I have a need for very persistent SCSI device naming.  As I understand
> the current SCSI device naming we have this:
> 
> Host:Channel:Target:Lun
> 
> If a new SCSI host is inserted into the machine, things move.  The
> implementation that I'm trying to imitate with udev uses the above four
> bits of info plus information regarding the position of the SCSI HBA
> that the device is plugged into.
> 
> What is the best way to do this with udev?

Is there anything unique about your devices you can rely on?  scsi
serial number?  vendor?  device type?  label id on the filesystem?

If you can find something, then use that in a udev rule.

thanks,

greg k-h


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2003-11-20 16:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-14  3:27 really persistent SCSI device naming Martin Hicks
2003-11-14  7:14 ` Ihno Krumreich
2003-11-20 16:54 ` Greg KH [this message]
2003-11-20 18:33 ` Martin Hicks

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=marc-linux-hotplug-106934858519797@msgid-missing \
    --to=greg@kroah.com \
    --cc=linux-hotplug@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).