From: "Paweł Gołaszewski" <blues@ds.pg.gda.pl>
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: Wed, 23 Apr 2003 15:49:54 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.51L.0304231547460.12634@piorun.ds.pg.gda.pl> (raw)
In-Reply-To: <1050859494.595.4.camel@teapot.felipe-alfaro.com>
On Sun, 20 Apr 2003, Felipe Alfaro Solana wrote:
> > Ok, i should learn to leave well enough alone, but i don't. After
> > successfully installing a monolithic 2.5.67 kernel i decided i wanted
> > modules, so i made them, and what happened, it hung after the initrd
> > initialized. So, when 2.5.68 came out i of course grab it,
> > compile/install it without a hitch, but for one thing, as of now make
> > install did not make an initrd for that install. Does anyone know how
> > to make this manually, it won't boot without one?
> 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?
initrd gives much more flexibility.
I can make one kernel and use it on _all_ of my mashines, just change
initrd. quick, nice and flexible with proper initrd tools set.
--
pozdr. Paweł Gołaszewski
---------------------------------
worth to see: http://www.againsttcpa.com/
CPU not found - software emulation...
next prev parent reply other threads:[~2003-04-23 13:38 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
2003-04-23 13:49 ` Paweł Gołaszewski [this message]
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.4.51L.0304231547460.12634@piorun.ds.pg.gda.pl \
--to=blues@ds.pg.gda.pl \
--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).