From: Roman Kagan <rkagan@mail.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] yaird, a mkinitrd based on hotplug concepts
Date: Tue, 22 Feb 2005 11:51:10 +0000 [thread overview]
Message-ID: <20050222115110.GB11284@katya> (raw)
In-Reply-To: <20050217210620.A20645@banaan.localdomain>
On Sat, Feb 19, 2005 at 03:00:53AM +0100, Erik van Konijnenburg wrote:
> - the classical method: pre-compute required modules and put only
> those on the image,
> - or the radical approach: put it all on the image and let hotplug
> sort it out at boot time.
>
> - The radical approach depends on a rewrite of hotplug without shell
> scripts (it's very difficult for mkinitrd to determine reliably which
> executables are needed by a shell script).
But this will probably be needed in your classical approach too (I mean
tracking of the required executables, I don't immediately see why shell
scripts are worse in this respect).
BTW one more item to track the dependencies for (in case you don't have
enough :) is the firmware files. You can identify which modules may
need firmware by checking their dependency on firmware_class, but I see
no way of knowing which firmware files they are going to request. To
make it worse, firmware is the (only) kind of hotplug events which can
be neither delayed (due to limited timeout) nor postponed to be replayed
later on.
Cheers,
Roman.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-02-22 11:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 20:06 [ANNOUNCE] yaird, a mkinitrd based on hotplug concepts Erik van Konijnenburg
2005-02-17 21:50 ` Jeff Garzik
2005-02-17 22:50 ` Roman Kagan
2005-02-19 2:00 ` Erik van Konijnenburg
2005-02-22 11:51 ` Roman Kagan [this message]
2005-02-22 17:48 ` Harald Hoyer
2005-02-22 19:26 ` Patrick Mansfield
2005-02-22 20:03 ` Roman Kagan
2005-02-22 21:25 ` Erik van Konijnenburg
2005-02-22 21:48 ` Erik van Konijnenburg
2005-02-22 22:57 ` Erik van Konijnenburg
2005-03-17 8:26 ` Werner Almesberger
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=20050222115110.GB11284@katya \
--to=rkagan@mail.ru \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).