Re: [klibc] klibc and what's the next step?

[Olaf Hering]

 On Tue, Jul 11, H. Peter Anvin wrote:

> It's a deployment problem, arguably especially for people who 
> cross-compile.  You have two major pieces of code (kernel and klibc) 
> which have to be changed at the same time, with different maintainers 
> and reviewers.

Why is that a problem? You cant rip code from the kernel before the main
kinit has support for that removed feature. Thats obvious.
I dont use suspend, so I dont know how the existing in-kernel code has to
look in kinit.
But for the partition discovery (the ROOT_DEV users) its likely less than
100 lines of code. And after all, root= exists. Probably not a big loss if
that code just disappears.

I dont get your point.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/