From: Olaf Hering <olaf@aepfle.de>
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 18:04:12 +0100 [thread overview]
Message-ID: <20070115170412.GA26414@aepfle.de> (raw)
In-Reply-To: <45AB8CB9.2000209@walrond.org>
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.
/sbin/hotplug and /init are two very different and unrelated things.
next prev parent reply other threads:[~2007-01-15 17:04 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 [this message]
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
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=20070115170412.GA26414@aepfle.de \
--to=olaf@aepfle.de \
--cc=andrew@walrond.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox