Re: 2.5.68 kernel no initrd
=?ISO-8859-2?Q?Pawe=B3_Go=B3aszewski?= (blues@ds.pg.gda.pl)
Wed, 23 Apr 2003 15:49:54 +0200 (CEST)
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...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/