From: Patrick Mansfield <patmans@us.ibm.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Re-ordering rules in config file gives different results when it should not
Date: Wed, 25 Feb 2004 01:30:24 +0000 [thread overview]
Message-ID: <20040224173024.A24945@beaverton.ibm.com> (raw)
In-Reply-To: <2F75A5CCEF1E6A4C8CA2E75CF7F529E901F26330@orsmsx409.jf.intel.com>
On Tue, Feb 24, 2004 at 04:00:31PM -0800, Sabharwal, Atul wrote:
> I have a sample config file below. Executing it just creates device
> entries
> Scsi_card_1 and host_scsi0. If I reo-order the rules, host_scsi1 gets
> Created and host_scsi0 is not created.
>
> Patrick, you were saying about bug with partitions. I ran scsi_id
> manually
Yes, partitions (what most people care about) won't match any RESULT
when PROGRAM is used to call scsi_id.
> To complete the RESULT field. I am assuming that I have created 6
> distinct
> Rules and till there is no success, the next rule will get selected.
> #scsi device 3.1
> BUS="scsi", ID="1:0:1:0", NAME="scsi_card_1"
>
> #scsi device /block/sda in sysfs
> PROGRAM="/sbin/scsi_id -p 0x80 -s /block/sda", BUS="scsi",
> RESULT="SSEAGATE ST318436LW 3BM07NKA000070456Z6B", NAME="host_scsi0"
Don't pass any options to scsi_id in the PROGRAM rule, not even the -p
0x80. If the device supports page 0x83, the RESULT *will* be different.
If the default behaviour does not work for some reason, and a line in
/etc/scsi_id.config.
But what is screwing up your rules is passing a sysfs device to scsi_id.
scsi_id -s /dev/sda in the rule is like asking "does /dev/sda have result
X?", instead of "does the current device have result X?".
i.e. the rule should be:
PROGRAM="/sbin/scsi_id", BUS="scsi", RESULT="SSEAGATE ST318436LW 3BM07NKA000070456Z6B", NAME="host_scsi0"
-- 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-25 1:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 0:00 Re-ordering rules in config file gives different results when it should not Sabharwal, Atul
2004-02-25 1:30 ` Patrick Mansfield [this message]
2004-02-25 2:04 ` Sabharwal, Atul
2004-02-25 2:13 ` Patrick Mansfield
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=20040224173024.A24945@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).