From: Mark Rustad <mrustad@gmail.com>
To: Andrew Walrond <andrew@walrond.org>
Cc: Olaf Hering <olaf@aepfle.de>,
Jan Engelhardt <jengelh@linux01.gwdg.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Initramfs and /sbin/hotplug fun
Date: Mon, 15 Jan 2007 21:50:01 -0600 [thread overview]
Message-ID: <91B1A3E1-A745-4EB3-893F-8AC7D2497FFF@gmail.com> (raw)
In-Reply-To: <45ABDBF5.9000900@walrond.org>
On Jan 15, 2007, at 1:54 PM, Andrew Walrond wrote:
> Olaf Hering wrote:
>> Why do you need /sbin/hotplug anyway, just for firmware loading for a
>> non-modular kernel?
>
> I guess this is unusual, but FWIW...
>
> I have a custom distro and I was just looking for the easiest way
> to create a bootable rescue pen-drive. So I just took a working
> distro, added an init->sbin/init symlink, cpio'ed it into an
> initramfs, and booted it up. Works a treat, except for the early
> hotplug calls.
I have a kernel that needs to have early hotplug calls to load
firmware. I just rolled my own simple hotplug scripts to only address
that issue and have not had a problem since. The mdev in busybox that
is in the gentoo initramfs didn't seem to be able to handle it, so I
just made my own scripts. In my case I needed QLogic firmware so root
could be on FC.
FWIW, it is a real PITA to not be able to build a monolithic kernel
that can bring up root on its own. I will stipulate that I am an old-
school guy that likes monolithic kernels, but I do feel that
something has been lost. Yes, I am aware of the reasons for the
change, else I would have written something when I was fighting the
battle, but I still don't have to like it.
--
Mark Rustad, MRustad@mac.com
next prev parent reply other threads:[~2007-01-16 3:50 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 [this message]
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=91B1A3E1-A745-4EB3-893F-8AC7D2497FFF@gmail.com \
--to=mrustad@gmail.com \
--cc=andrew@walrond.org \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
/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
all inboxes | Powered by JetHome®