From: Olaf Hering <olaf@aepfle.de>
To: Andrew Walrond <andrew@walrond.org>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Initramfs and /sbin/hotplug fun
Date: Mon, 15 Jan 2007 18:54:37 +0100 [thread overview]
Message-ID: <20070115175437.GA26944@aepfle.de> (raw)
In-Reply-To: <45ABBB8B.6000505@walrond.org>
On Mon, Jan 15, Andrew Walrond wrote:
> >/sbin/hotplug and /init are two very different and unrelated things.
>
> Well, of course. But looking at the thread provided by Jan, it seems the
> kernel might not be in any fit state to service the (userspace) hotplug
> infrastructure when it makes the calls (Ie can't create pipes yet).
Thats because noone really fixed the init call order. Its going back and
forth since /init was added in 2.6.6.
Ideally, there could be some /earlyinit that could prepare the
enviroment for hotplug calls.
Why do you need /sbin/hotplug anyway, just for firmware loading for a
non-modular kernel?
next prev parent reply other threads:[~2007-01-15 17:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 14:16 Initramfs and /sbin/hotplug fun Andrew Walrond
2007-01-15 16:44 ` Jan Engelhardt
2007-01-15 17:04 ` Olaf Hering
2007-01-15 17:36 ` Andrew Walrond
2007-01-15 17:54 ` Olaf Hering [this message]
2007-01-15 19:54 ` Andrew Walrond
2007-01-16 3:50 ` Mark Rustad
2007-01-15 19:43 ` Bill Davidsen
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=20070115175437.GA26944@aepfle.de \
--to=olaf@aepfle.de \
--cc=andrew@walrond.org \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@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.