linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bauke Jan Douma <bjdouma@xs4all.nl>
To: linux-hotplug@vger.kernel.org
Subject: Re: hotplug-ng
Date: Fri, 02 Feb 2007 18:13:32 +0000	[thread overview]
Message-ID: <45C37F4C.3020809@xs4all.nl> (raw)
In-Reply-To: <OF450063C4.8C650338-ONC1256FC4.0034B8EC-C1256FC4.0036DB70@philips.com>

Dan Nicholson wrote on 02-02-07 18:50:
> [..deletia...]
> The right way to do this is to tell the kernel to not use anything for
> the event handler since udev will handle this on it's own.
> 
> echo "" > /proc/sys/kernel/hotplug
> 
> I'm pretty sure everybody using udev does this in their init script.

I do.
Which is not to say udev isn't a hell hole ;-)
But it's a rewarding hello hole when you
(finally) get it right.


> 
> --
> Dan

bjd



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
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

      parent reply	other threads:[~2007-02-02 18:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-14  9:58 hotplug-ng andreas.walden
2005-03-14 10:04 ` hotplug-ng Marco d'Itri
2007-02-02 11:44 ` hotplug-ng Chris Steel
2007-02-02 12:26 ` hotplug-ng Marco d'Itri
2007-02-02 13:29 ` hotplug-ng Chris Steel
2007-02-02 13:44 ` hotplug-ng Marco d'Itri
2007-02-02 18:13 ` Bauke Jan Douma [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=45C37F4C.3020809@xs4all.nl \
    --to=bjdouma@xs4all.nl \
    --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).