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 [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
