From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: Bill Davidsen <davidsen@tmr.com>
Cc: "Kevin P. Fleming" <kpfleming@cox.net>,
LKML <linux-kernel@vger.kernel.org>,
"Paweł Gołaszewski" <blues@ds.pg.gda.pl>,
"Dave Mehler" <dmehler26@woh.rr.com>
Subject: Re: 2.5.68 kernel no initrd
Date: 24 Apr 2003 23:54:03 +0200 [thread overview]
Message-ID: <1051221242.612.49.camel@teapot.felipe-alfaro.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1030424161618.11351B-100000@gatekeeper.tmr.com>
On Thu, 2003-04-24 at 22:19, Bill Davidsen wrote:
> > I don't have any doubts that initrd is a very flexible solution and
> > provides for a generic kernel. However, in the end (I'm talking about my
> > experiences), initrd has caused me more troubles than problems it
> > solved. I always keep all "config" file for every kernel I use on my
> > machines.
>
> Other than needing to build and maintain all those kernels, what does it
> gain you over installing the modules you need and having a single kernel?
Simply said, I don't like "initrd". I have still to figure out how to
make an "initrd" that includes the newer modutils.
Anyways, I don't mantain so much kernels (only 3 or 4 different
versions), and have a mix of AMD/P4/P3/P2/PI machines that need things
that can't be configured/don't yet work as modules, so I prefer to pass
initrd by...
--
Please AVOID sending me WORD, EXCEL or POWERPOINT attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html
Linux Registered User #287198
prev parent reply other threads:[~2003-04-24 21:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-20 4:39 Dave Mehler
2003-04-20 17:24 ` Felipe Alfaro Solana
2003-04-22 21:58 ` Bill Davidsen
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 [this message]
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=1051221242.612.49.camel@teapot.felipe-alfaro.com \
--to=felipe_alfaro@linuxmail.org \
--cc=blues@ds.pg.gda.pl \
--cc=davidsen@tmr.com \
--cc=dmehler26@woh.rr.com \
--cc=kpfleming@cox.net \
--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
all inboxes | Powered by JetHome®