linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Udev and SCSI/Fiber channel devices
Date: Tue, 24 Feb 2004 11:22:36 +0000	[thread overview]
Message-ID: <1077621755.1119.9.camel@pim> (raw)
In-Reply-To: <2F75A5CCEF1E6A4C8CA2E75CF7F529E901F260D7@orsmsx409.jf.intel.com>

On Tue, 2004-02-24 at 05:58, Patrick Mansfield wrote:
> On Tue, Feb 24, 2004 at 03:22:14AM +0100, Kay Sievers wrote:
> > On Tue, 2004-02-24 at 03:09, Sabharwal, Atul wrote:
> > >  You can use scsi_id in a callout rule with udev for scsi persistent
> > > names.
> > > scsi_id is released along with udev under extras/scsi_id.
> > > >>  I tried a callout rule as follows :
> > > 
> > >      CALLOUT="/sbin/scsid -p 0x80 -s /block/sda| awk ' {}; end { print$3 }'", BUS="scsi", ID="325687809", NAME="host_scsi"
> 
> It's scsi_id, not scsid.
> 
> Should udev log an error if it can't find the CALLOUT program?

It does, but only with DEBUG=true.
I will have a look. We may change some critical debug to info().

> You don't need any arguments, scsi_id relies on the environment variable
> DEVPATH for the sysfs path, though it might be cleaner if we could use a
> udev string substitution.
> 
> And, make sure you have at least one line in your /etc/scsi_id.config
> like:
> 
> 	options=-g
> 
> I will add a udev example to the scsi_id man page, and more about its
> behaviour when called with no arguments, though the udev man has a fine
> example.
> 
> DEVPATH should probably be documented somewhere, maybe in hotplug(8). (I
> can't find anything about it in man pages of udev, udevinfo, or hotplug.)

Strange, hotplug(8) mentions ACTION but not DEVPATH.
I will prepare a patch fot hotplug and put a few words in SYNOPSIS of
udev, tonight. 

> > Huh, do we really need this complex callout argument line.
> > We are not prepared for something like this, cause we pass
> > only 7 arguments down to the program.
> > If it's really needed, I can have look.
> > Pat?
> 
> No. The above rule should just be:
> 
> BUS="scsi", CALLOUT="/sbin/scsi_id", ID="325687809", NAME="your_disk"

Nice, so we can stay with the current logic.

thanks,
Kay



-------------------------------------------------------
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 11:22 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 [this message]
2004-02-24 17:03 ` Sabharwal, Atul
2004-02-24 17:32 ` Patrick Mansfield
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=1077621755.1119.9.camel@pim \
    --to=kay@vrfy.org \
    --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).