[...]
> > And how do you know .config is not the problem? You may just be downloading
> > bad versions of the source. See if you have the *exact same* problems with
> > the kernels from ftp.kernel.org. If you do not, then it is *not* Linus'
> > fault, but the fault of who you are getting the kernel from.
> I know it's not, as you say, the ".config". You see, I am an expert.
> The problem is that initial RAM disk support, and memory managment
> associated with it, has been abandoned in the development kernels.
It has not been "abandoned", it has note been updated to changed internal
interfaces yet. And "initrd doesn't compile with the latest development
kernels" is _far_ from "Latest kernels don't compile at all. Distributions
have secret kernel sources they won't share, just to screw the Linux
community".
> Since the only way I can justify working on Linux on company time
> is to work on the versions that we are using in our embeded Linux
> project, it is mandatory that I enable "initrd" support because I
> can't boot the target without it. Enabling "initrd" support causes
> compilation failures. There are a few other things I need also.
If you need a production kernel, stick to 2.2.x, at most check out Alan
Cox' 2.2.14pre series. Or stay with the (patched) source from your
distribution. Or, if you are looking forward, experiment a bit with 2.3.x
to see what 2.4 has in store.
-- Horst von Brand vonbrand@sleipnir.valparaiso.cl Casilla 9G, Viņa del Mar, Chile +56 32 672616- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/