linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Mansfield <patmans@us.ibm.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Udev and SCSI/Fiber channel devices
Date: Tue, 24 Feb 2004 17:32:48 +0000	[thread overview]
Message-ID: <20040224093247.A19485@beaverton.ibm.com> (raw)
In-Reply-To: <2F75A5CCEF1E6A4C8CA2E75CF7F529E901F260D7@orsmsx409.jf.intel.com>

On Tue, Feb 24, 2004 at 09:03:39AM -0800, Sabharwal, Atul wrote:
>  I tried /sbin/scsi_id also: So, tried combination #1 & #2.  Do we need
> the method prefix or
> Its implied.  Somewhere in the documentation, there were examples based
> on PCI slot number
> But there was no prefix TOPOLOGY.  
> 
> 1.  CALLOUT, PROGRAM="/sbin/scsid -p 0x80 -s /block/sda| awk ' {}; end {
> print$3 }'", BUS="scsi", ID="325687809", NAME="host_scsi"
> 
> 2.  PROGRAM="/sbin/scsid -p 0x80 -s /block/sda| awk ' {}; end { print$3
> }'", BUS="scsi", ID="325687809", NAME="host_scsi"
> 
> --
> Atul

Yes, that should have been PROGRAM not CALLOUT in my previous email, as
there is no CALLOUT, so the rule should be like:

BUS="scsi", PROGRAM="/sbin/scsi_id", ID="325687809", NAME="your_disk"

But what is the output of:

/sbin/scsi_id -s /block/sda

Whatever the result is what you want in the ID field.

And, you need a line like this in your /etc/scsi_id.config:

	options=-g

-- Patrick Mansfield


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&op=click
_______________________________________________
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:[~2004-02-24 17:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-23 23:43 Udev and SCSI/Fiber channel devices Sabharwal, Atul
2004-02-24  1:19 ` Greg KH
2004-02-24  1:23 ` Patrick Mansfield
2004-02-24  1:33 ` Sabharwal, Atul
2004-02-24  2:06 ` Greg KH
2004-02-24  2:09 ` Sabharwal, Atul
2004-02-24  2:22 ` Kay Sievers
2004-02-24  4:58 ` Patrick Mansfield
2004-02-24 11:22 ` Kay Sievers
2004-02-24 17:03 ` Sabharwal, Atul
2004-02-24 17:32 ` Patrick Mansfield [this message]
2004-02-24 18:03 ` Sabharwal, Atul
2004-02-24 18:11 ` Sabharwal, Atul
2004-02-24 18:16 ` Kay Sievers
2004-02-24 18:19 ` Greg KH
2004-02-24 18:20 ` Sabharwal, Atul
2004-02-24 18:24 ` Sabharwal, Atul
2004-02-24 18:31 ` Patrick Mansfield
2004-02-24 18:40 ` Greg KH

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=20040224093247.A19485@beaverton.ibm.com \
    --to=patmans@us.ibm.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).