From: Manuel Reimer <Manuel.Spam@nurfuerspam.de>
To: linux-kernel@vger.kernel.org
Subject: Re: udev: Inconsistency between %b and %p?
Date: Tue, 11 Sep 2007 16:11:36 +0200 [thread overview]
Message-ID: <fc67c1$vci$1@sea.gmane.org> (raw)
In-Reply-To: <3ae72650709061803u7ed2ff21v511f219e742ecd7a@mail.gmail.com>
Kay Sievers wrote:
>>>> ATTRS{idVendor}=="0dda", ATTRS{idProduct}=="2005", SUBSYSTEM=="scsi",
>>>> ACTION=="add", PROGRAM+="/usr/bin/test.sh %b %p"
> It's fine. $id, like some other values too, is a value of the device
> where all keys successful matched while walking up the chain of
> devices.
But the "SUBSYSTEM" didn't match for the USB-device.
I still don't know, what %b contains and in which situation the value in
%b may help anyone.
> Seems you are looking for the name of the device you received the
> event for, so just use $kernel instead.
Yes, this did the job. Thanks for the hint.
CU
Manuel
prev parent reply other threads:[~2007-09-11 14:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 15:33 udev: Inconsistency between %b and %p? Manuel Reimer
2007-09-06 15:57 ` Andreas Schwab
2007-09-06 21:05 ` Manuel Reimer
2007-09-06 21:46 ` Andreas Schwab
2007-09-06 21:59 ` Manuel Reimer
2007-09-07 1:03 ` Kay Sievers
2007-09-11 14:11 ` Manuel Reimer [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='fc67c1$vci$1@sea.gmane.org' \
--to=manuel.spam@nurfuerspam.de \
--cc=linux-kernel@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