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 18:31:42 +0000 [thread overview]
Message-ID: <20040224103142.A20330@beaverton.ibm.com> (raw)
In-Reply-To: <2F75A5CCEF1E6A4C8CA2E75CF7F529E901F260D7@orsmsx409.jf.intel.com>
On Tue, Feb 24, 2004 at 10:11:31AM -0800, Sabharwal, Atul wrote:
> The output of command /sbin/scsi_id -s /block/sda giver <vendor, model,
> serialnumber> .
> I can put -p 0x80 but it defaults to page 0x80 anyway.
>
> The reason to separate the three field with awk was to have exact match
> without worrying
> about spaces. Putting vendor, model number information in a udev rule
> does not belong
> Over there. In fact, if like scsi_id, it was okay to have an custom
> callout programs
> And use their output to match the RESULT field, that would be great.
It's normal to use vendor and model in udev rules.
Page 0x80 gives a unique serial number only for a given vendor and model,
so if you use only the serial number, it is possible though perhaps
unlikely that it will collide with other ID's.
> The reason I am explotring CALLOUT is to have a method to give
> persistant device names
> Using bus#, chasis# & slot#.
If you want to name based on position or hardware location you don't want
to use scsi_id, you probably want to key off of the bus id, plus other
sysfs host adapter (i.e. pci) attributes.
-- 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
next prev parent reply other threads:[~2004-02-24 18:31 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
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 [this message]
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=20040224103142.A20330@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).