From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: RESULT is not matching
Date: Wed, 22 Jun 2005 22:40:25 +0000 [thread overview]
Message-ID: <20050622224025.GB4576@vrfy.org> (raw)
In-Reply-To: <7795111404396@lycos-europe.com>
On Wed, Jun 22, 2005 at 10:28:34PM +0000, (' wrote:
> <html><head><style type="text/css">body{font:12px Arial;margin:3px;overflow-y:auto;overflow-x:auto}p{margin:0px;}blockquote, ol, ul{margin-top:0px;margin-bottom:0px;}</style></head>
>
> <body><div style="display: block; font-family: Arial; font-size: 12px;">Hi,<br>
> <br>
> I've written a couple of udev.rules that should identify 2 disks using
> the UUID obtained from scsi_id. I have been running udev.debug and
> checking the debug information out to /var/log/messages and I find that
> the output from scsi_id never matches my RESULT ... even though i think
> it should.<br>
> <br>
> So here are the rules:<br>
> BUS="scsi", PROGRAM="/sbin/scsi_id -g -s /block/%k", RESULT="200000e1100a35065", NAME="disk-sda%n"<br>
> <br>
> BUS="scsi", RESULT="200000e1100a34fef", NAME="disk-sdb%n"<br>
> BUS="scsi", RESULT="3600508b4000151bf0001e000015b0000", NAME="sues-sdc", SYMLINK="tester"<br>
> BUS="scsi", RESULT="3600508b4000151bf0001e00001610000", NAME="sues-sdd"<br>
> <br>
> And here are a few of the lines from the messages file ...<br>
> <br>
> Jun 23 01:04:00 rx1620-1 udev[12450]: namedev_name_device: process rule<br>
> Jun 23 01:04:00 rx1620-1 udev[12450]: match_rule: check for BUS dev->bus='scsi' sysfs_device->bus='scsi'<br>
> Jun 23 01:04:00 rx1620-1 udev[12450]: match_rule: BUS matches<br>
> Jun 23 01:04:00 rx1620-1 udev[12450]: match_rule: check for RESULT
> dev->result='3600508b4000151bf0001e00001610000',
> udev->program_result='3600508b4000151bf0001e00001610000 '<br>
Please try if RESULT="200000e1100a35065*" works.
Kay
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id\x16492&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
prev parent reply other threads:[~2005-06-22 22:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-22 22:28 RESULT is not matching ('
2005-06-22 22:40 ` Kay Sievers [this message]
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=20050622224025.GB4576@vrfy.org \
--to=kay.sievers@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).