Messages in this thread | | | Subject | Re: 2.5.68 kernel no initrd | From | Felipe Alfaro Solana <> | Date | 24 Apr 2003 23:54:03 +0200 |
| |
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
- 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/
| |