All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Walrond <andrew@walrond.org>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Initramfs and /sbin/hotplug fun
Date: Mon, 15 Jan 2007 14:16:25 +0000	[thread overview]
Message-ID: <45AB8CB9.2000209@walrond.org> (raw)

If the initramfs root filesystem contains /sbin/hotplug, the kernel 
starts calling it very early in the kernel boot process, well before 
/init has been called. In my case this resulted in lots of hotplug 
segfault messages as the kernel boots, followed by a thoroughly unhappy 
hotplug+udev once /init actually gets control.

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?

Andrew Walrond

             reply	other threads:[~2007-01-15 14:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-15 14:16 Andrew Walrond [this message]
2007-01-15 16:44 ` Initramfs and /sbin/hotplug fun 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

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=45AB8CB9.2000209@walrond.org \
    --to=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 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.