From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Wed, 08 Aug 2007 02:48:49 +0000 Subject: Re: hotplug not opening stdin by default. Is this a bug? Message-Id: <20070808024849.GA5305@kroah.com> List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Tue, Aug 07, 2007 at 06:47:55PM -0500, Leif Johnson wrote: > > What do you mean by "hotplug"? The normal hotplug scripts are just > > that, scripts. Are you running some other binary for hotplug instead? > It is using /sbin/hotplug which is a shell script (/bin/sh). This is > a version of ash on BusyBox. > The exact calling is > /sbin/hotplug (/bin/sh) -> bus specific hotplug (also /bin/sh) -> c program. > > Neither of the shell scripts does anything special with stdin, stdout or stderr. > > Is the consensus that /sbin/hotplug should do something with those > fds? (Connect to /dev/null). If you want to do something like that with it, sure, go ahead, no one is stopping you :) You do realize that the /sbin/hotplug interface is deprecated and not really recommended to use anymore, right? Why not just use udev? And yes, embedded systems us udev all the time, it works quite well on memory and size constrained systems. thanks, greg k-h ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ 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