lkml.org 
[lkml]   [2006]   [Jul]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [klibc] klibc and what's the next step?
 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@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-07-11 20:03    [W:0.165 / U:0.160 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site