From: Bill Davidsen <davidsen@tmr.com>
To: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
Cc: Dave Mehler <dmehler26@woh.rr.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.68 kernel no initrd
Date: Tue, 22 Apr 2003 17:58:44 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.3.96.1030422175506.31749B-100000@gatekeeper.tmr.com> (raw)
In-Reply-To: <1050859494.595.4.camel@teapot.felipe-alfaro.com>
On 20 Apr 2003, Felipe Alfaro Solana wrote:
> I don't have experience with initrd, but why would you want a initrd?
> Can't you simply build into the kernel the required pieces to mount the
> root filesystem and leave the rest as loadable modules?
As long as you are suporting or testing a small number of configurations,
say less than two, initrd buys not much. But using all modules allows you
to support a new config just by rebuilding initrd, vastly faster than
building a kernel on most machines. And for a vendor doing a distribution
it is a huge win.
Not to mention some drivers work differently when loaded as modules,
loading as modules allows control of the device scans, etc, etc. It's just
more flexible.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
next prev parent reply other threads:[~2003-04-22 21:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-20 4:39 2.5.68 kernel no initrd Dave Mehler
2003-04-20 17:24 ` Felipe Alfaro Solana
2003-04-22 21:58 ` Bill Davidsen [this message]
2003-04-23 13:49 ` Paweł Gołaszewski
2003-04-23 16:00 ` Valdis.Kletnieks
2003-04-23 16:36 ` Kevin P. Fleming
2003-04-23 21:54 ` Felipe Alfaro Solana
2003-04-24 20:19 ` Bill Davidsen
2003-04-24 21:54 ` Felipe Alfaro Solana
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=Pine.LNX.3.96.1030422175506.31749B-100000@gatekeeper.tmr.com \
--to=davidsen@tmr.com \
--cc=dmehler26@woh.rr.com \
--cc=felipe_alfaro@linuxmail.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;
as well as URLs for NNTP newsgroup(s).