LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Andrew Walrond <andrew@walrond.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Initramfs and /sbin/hotplug fun
Date: Mon, 15 Jan 2007 14:43:34 -0500	[thread overview]
Message-ID: <45ABD966.7030207@tmr.com> (raw)
In-Reply-To: <45ABBB8B.6000505@walrond.org>

Andrew Walrond wrote:
> Olaf Hering wrote:
>> On Mon, Jan 15, Andrew Walrond wrote:
>>
>>> To solve this, I deleted /sbin/hotplug from the initramfs archive and 
>>> modified /init to reinstate it once it gets control. This works fine, 
>>> but seems inelegant. Is there a better solution? Should sbin/hotplug 
>>> be called at all before the kernel has passed control to /init?
>>
>> Yes, it should be called.
> 
> Ok
> 
>> /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).
> 
> The kernel wouldn't call /init (or /sbin/init) before it was fully ready 
> to handle userspace processes, so why should it feel able to call the 
> hotplug userspace?
> 
I could speculate in case it needs to hotplug something to complete 
boot, but it could just be a thinko.

-- 
bill davidsen <davidsen@tmr.com>
   CTO TMR Associates, Inc
   Doing interesting things with small computers since 1979

      parent reply	other threads:[~2007-01-15 19:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-15 14:16 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
2007-01-15 19:54       ` Andrew Walrond
2007-01-16  3:50         ` Mark Rustad
2007-01-15 19:43     ` Bill Davidsen [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=45ABD966.7030207@tmr.com \
    --to=davidsen@tmr.com \
    --cc=andrew@walrond.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: Initramfs and /sbin/hotplug fun' \
    /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

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).