On Tue, Jul 15, 2008 at 08:51:33PM -0400, Theodore Tso wrote: > For one reason, because there's more than one mkinitrd. FC9 ships > with mkinitrd 6.0.52; OpenSuSE ships with mkinitrd 2.1, and the > sources don't look even vaguely similar to one another. Right. Other than name, they've historically shared nothing. Both have grown through the evolution of multiple distros, requiring different workarounds in each due to differences in CONFIG_ options in the kernel between vendors for eg. Whilst it would be great for unified development on the tools that create the early boot process, I think it's a non-starter due to the fact that you can't really do it without throwing out everything you already have today. The same reason imo, that hpa's klibc work hasn't gained mass-appeal from vendors. Even if we had a 'reference' mkinitrd in the kernel, it would be pretty much useless until it reached feature parity with every distros existing tools, and if everyone uses those instead of furthering the reference implementation, it fails on the starting blocks. Dave -- http://www.codemonkey.org.uk --
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Glauber de Oliveira Costa | [PATCH 16/19] provide tss_desc |
| Greg KH | [patch 00/60] 2.6.26-stable review |
git: | |
| Nick Piggin | [rfc][patch 2/3] slab: introduce SMP alignment |
| Hannes Eder | [PATCH 00/43] drivers/net: fix (sparse) warnings |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | [GIT]: Networking |
