From: "Kay Sievers" <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Make udev re-process the rules database?
Date: Thu, 03 Jul 2008 18:38:49 +0000 [thread overview]
Message-ID: <3ae72650807031138v30e08099xf9a423ebfbbe86bd@mail.gmail.com> (raw)
In-Reply-To: <20080703172941.GD24665@one-eyed-alien.net>
On Thu, Jul 3, 2008 at 19:29, Matthew Dharm
<mdharm-usb@one-eyed-alien.net> wrote:
> Is there a way to easily make udev re-process the rules database?
>
> The scenario I found was when I was messing with rules that applied to
> ttyS[0-3]. I would change a rule, and then I couldn't figure out how to
> simulate a removal/insertion event to test the new rule.
>
> Yes, I could use some udev tools to get a simulation of what the rules
> would do, but that's not the same thing. And, depending on what I was
> changing, the simulation would not give me correct information about what
> would happen.
>
> I wound up doing a lot of rebooting... but is there an easier way?
Echo "remove"/"add" to /dev$DEVPATH/uevent?
Kay
prev parent reply other threads:[~2008-07-03 18:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 17:29 Make udev re-process the rules database? Matthew Dharm
2008-07-03 18:13 ` Greg KH
2008-07-03 18:38 ` 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=3ae72650807031138v30e08099xf9a423ebfbbe86bd@mail.gmail.com \
--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).