From: "J. Bakshi" <j.bakshi@unlimitedmail.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: how to generate udv trigger for a specific device ?
Date: Fri, 29 Oct 2010 11:31:16 +0000 [thread overview]
Message-ID: <201010291118.o9TBIvf1025030@dcnode-02.unlimitedmail.net> (raw)
In-Reply-To: <201010280447.o9S4lDZG001183@dcnode-01.unlimitedmail.net>
Any clue please ?
On Thu, 28 Oct 2010 10:17:21 +0530
"J. Bakshi" <j.bakshi@unlimitedmail.org> wrote:
> Hello list,
>
> I'm a newbie in udev rules and writing some very specific udev rules for my usb mouse. As per sysfs the mouse is detected as /sys/class/input/input11 and [ udevadm monitor /sys/class/input/input11 ] proves the detection. Now to test my udev rules which execute some action based on add / remove of the mouse, I have to physically add / remove the mouse. And for each and every change in my ruleset I have to do the same. Is there any way to generate the event by udevadm, so that my rules are fired based on the generated event ? I have tried by
>
> ````````````
> udevadm trigger --verbose --sysname-match=/sys/class/input/input11 actiond
> ``````````````
>
> But no luck. Could anyone please help me to generate the required event with udevadm please ?
> Also interested to know, how to monitor the rules in action when the proper event is generated.
>
> With regards
> J. Bakshi
--
_____________________________________________________________________________
"Programming today is a race between software engineers striving to build
bigger and better idiot-proof programs and the universe trying to produce
bigger and\better idiots. So far, the universe is winning."
::::::Richard Cook
_____________________________________________________________________________
***************************************************************************************
Disclaimer : The information contained in this Message is confidential and
intended only for the use of the individual or entity identified. If the
reader of this message is not the intended recipient, any dissemination,
distribution or copying of the information contained in this message is
strictly prohibited. If you received this message in error, please notify the
sender immediately
***************************************************************************************
prev parent reply other threads:[~2010-10-29 11:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 4:59 how to generate udv trigger for a specific device ? J. Bakshi
2010-10-28 4:59 ` J. Bakshi
2010-10-28 4:59 ` J. Bakshi
2010-10-29 11:31 ` J. Bakshi [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=201010291118.o9TBIvf1025030@dcnode-02.unlimitedmail.net \
--to=j.bakshi@unlimitedmail.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