Message-ID: <45ABBB8B.6000505@walrond.org>
Date: Mon, 15 Jan 2007 17:36:11 +0000
From: Andrew Walrond <andrew@walrond.org>
User-Agent: Thunderbird 1.5.0.9 (X11/20070103)
MIME-Version: 1.0
To: Olaf Hering <olaf@aepfle.de>, Jan Engelhardt <jengelh@linux01.gwdg.de>
CC: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Initramfs and /sbin/hotplug fun
References: <45AB8CB9.2000209@walrond.org> <20070115170412.GA26414@aepfle.de>
In-Reply-To: <20070115170412.GA26414@aepfle.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1099
Lines: 29

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?

Andrew Walrond

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/