Messages in this thread | | | Date | Tue, 22 Apr 2003 17:58:44 -0400 (EDT) | From | Bill Davidsen <> | Subject | Re: 2.5.68 kernel no initrd |
| |
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.
- 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/
| |