From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Yet another UDEV question
Date: Tue, 28 Nov 2006 22:29:49 +0000 [thread overview]
Message-ID: <20061128222949.GB16152@kroah.com> (raw)
In-Reply-To: <335DD0B75189FB428E5C32680089FB9F80415D@mtk-sms-mail01.digi.com>
On Tue, Nov 28, 2006 at 02:55:48PM -0600, Kilau, Scott wrote:
> Hi everyone,
>
> Sorry to bug again.
>
> What is the "proper" way to inform the udev subsystem
> that I have added some new rules in /etc/udev/rules.d ?
>
> I did see this from:
> http://www.reactivated.net/writing_udev_rules.html
>
> > If your kernel does not have inotify support,
> > new rules will not be detected automatically.
> > In this situation, you must run udevcontrol reload_rules
> > after making any rule file modifications for those
> > modifications to take effect.
>
> The problem is that Red Hat AS/ES/WS 4 does not have the "udevcontrol"
> command.
>
> Is it fair to say that if "udevcontrol" does not exist,
> then hunting down the process id of "udevd", and sending
> it a kill -HUP would work okay?
>
> Or is there a better way to do it under distros that do not have
> "udevcontrol"?
Ick, RH4 is pretty old for udev. I'd suggest asking RH for what to do
here, as that system is pretty far off of mainline for a variety of
different things (kernel and udev). They might have added inotify, and
you could be fine.
thanks,
greg k-h
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
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:[~2006-11-28 22:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 20:55 Yet another UDEV question Kilau, Scott
2006-11-28 22:29 ` Greg KH [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=20061128222949.GB16152@kroah.com \
--to=greg@kroah.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).