From: "Dave Dodge" <dododge@smart.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: ANNOUNCE: User-space System Device Enumation (uSDE)
Date: Fri, 31 Oct 2003 02:29:26 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-106815267222508@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106738160829698@msgid-missing>
Greg KH writes:
> On Thu, Oct 30, 2003 at 07:45:08PM -0500, David Dodge wrote:
[...]
> > Mainly I'm asking because I did try putting a hotplug script into an
> > initramfs a few weeks ago (using -test7), and it didn't appear to be
> > invoked for e.g. the VESA framebuffer. So I want to make sure this is a
> > "future" capability and not something that should have worked :-)
>
> This is something that should have worked for you today, /sbin/hotplug
> does get called during early boot, before init is started up.
Okay, I'll keep working at it. Unfortunately my main test system has
since had a major hardware failure and I haven't gotten a replacement
set up yet.
In the meantime, from a quick look at the kernel code I see this:
- invocations of /sbin/hotplug normally go through call_usermodehelper.
- kernel/kmod.c: call_usermodehelper does this prior to scheduling
any work:
if (!system_running)
return -EBUSY;
- init/main.c: system_running is not set non-zero until just
prior to starting init.
So it looks like calls to hotplug are dropped while compiled-in
drivers are initializing. Or am I missing something obvious? I
needed a one-line patch to be able to boot into initramfs; do I need
another to enable call_usermodehelper earlier?
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
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
next prev parent reply other threads:[~2003-10-31 2:29 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-28 22:44 ANNOUNCE: User-space System Device Enumation (uSDE) Greg KH
2003-10-29 5:12 ` Guo, Min
2003-10-29 7:41 ` wwp
2003-10-29 16:10 ` Steven Dake
2003-10-29 19:04 ` Greg KH
2003-10-29 19:05 ` Greg KH
2003-10-30 16:09 ` A. Craig West
2003-10-31 0:45 ` David Dodge
2003-10-31 0:58 ` Greg KH
2003-10-31 2:29 ` Dave Dodge [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-31 0:45 David Dodge
2003-10-31 0:58 ` Greg KH
2003-10-31 0:58 ` Greg KH
2003-10-31 2:29 ` Dave Dodge
2003-10-29 5:12 Guo, Min
2003-10-29 5:12 ` Guo, Min
2003-10-29 16:10 ` Steven Dake
2003-10-29 16:10 ` Steven Dake
2003-10-29 19:04 ` Greg KH
2003-10-27 20:41 Mark Bellon
2003-10-27 21:00 ` Lars Marowsky-Bree
2003-10-27 21:14 ` Mark Bellon
2003-10-28 11:00 ` Lars Marowsky-Bree
2003-10-28 11:00 ` Lars Marowsky-Bree
2003-10-28 18:12 ` Steven Dake
2003-10-28 18:12 ` Steven Dake
2003-10-28 22:44 ` Greg KH
2003-10-29 14:30 ` Andreas Jellinghaus
2003-10-29 17:20 ` Daniel Stekloff
2003-11-02 17:28 ` Andreas Jellinghaus
2003-11-03 23:29 ` Daniel Stekloff
2003-10-29 19:18 ` Greg KH
2003-10-29 22:12 ` Andreas Jellinghaus
2003-10-29 22:43 ` Greg KH
2003-10-27 23:15 ` Steven Dake
2003-10-27 23:19 ` Mark Bellon
2003-10-27 20:40 Mark Bellon
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=marc-linux-hotplug-106815267222508@msgid-missing \
--to=dododge@smart.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.