From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev and hotplug
Date: Thu, 12 Oct 2006 12:48:01 +0000 [thread overview]
Message-ID: <1160657281.12323.8.camel@pim.off.vrfy.org> (raw)
In-Reply-To: <dvkdta$4ai$1@sea.gmane.org>
On Wed, 2006-10-11 at 21:06 +1000, Gioele Barabucci wrote:
> On Wednesday 11 October 2006 19:28, Kay Sievers wrote:
> > > "cat /proc/sys/kernel/hotplug" shows "/sbin/hotplug". But there is
> > > no file as "/sbin/hotplug".
> >
> > That's good not to have /sbin/hotplug. Even when there is no program to
> > fork anymore, you should disable the forking by the kernel, by setting
> > it to "".
> Will there be a kernel option to disable the creation
> of /proc/sys/kernel/hotplug altogether?
There is nothing planned. We could have an option that allows us to set
the default value in the kernel config, which could be an empty string
instead of /sbin/hotplug then. For now, we just do:
echo > /sys/kernel/uevent_helper
Kay
-------------------------------------------------------------------------
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
prev parent reply other threads:[~2006-10-12 12:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-19 20:12 udev and hotplug Andreas Jellinghaus
2006-03-20 0:49 ` Kay Sievers
2006-10-11 9:21 ` Raj Kumar Yadav
2006-10-11 9:28 ` Kay Sievers
2006-10-11 11:06 ` Gioele Barabucci
2006-10-12 12:48 ` 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=1160657281.12323.8.camel@pim.off.vrfy.org \
--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).