linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: hotplug not opening stdin by default. Is this a bug?
Date: Tue, 07 Aug 2007 23:17:15 +0000	[thread overview]
Message-ID: <20070807231715.GA768@kroah.com> (raw)
In-Reply-To: <dbe795460708071448h6cd82f1alc4e80953b41960f1@mail.gmail.com>

On Tue, Aug 07, 2007 at 04:48:18PM -0500, Leif Johnson wrote:
> Hello,
> 
> I ran into a problem that I believe is a bug in hotplug, but others do
> not agree.  So I am asking here.
> 
> This work is all being done on an embedded device, arm processor.
> Linux kernel 2.6.15,  .BusyBox v1.1.3, and libc 2.3.6.
> 
> Hotplug does not seem to open fds 0 or 2 on the system (and I'm told
> it does not do it on any system).

What do you mean by "hotplug"?  The normal hotplug scripts are just
that, scripts.  Are you running some other binary for hotplug instead?

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

  parent reply	other threads:[~2007-08-07 23:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-07 21:48 hotplug not opening stdin by default. Is this a bug? Leif Johnson
2007-08-07 22:16 ` Kay Sievers
2007-08-07 23:17 ` Greg KH [this message]
2007-08-07 23:47 ` Leif Johnson
2007-08-08  2:48 ` Greg KH

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=20070807231715.GA768@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).