[lkml]   [2006]   [Jun]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subjectklibc and what's the next step?

On Sun, 25 Jun 2006, H. Peter Anvin wrote:

> The majority of the patches are independent in the sense that they
> should apply independently, but Makefile/Kbuild files may have to be
> adjusted to build a partially patched tree.

I could now repeat all the concerns I already mentioned, why it shouldn't
be merged as is (that doesn't mean it shouldn't be merged at all!), but
they have been pretty much ignored anyway...

What I'm more interested in is basically answering the question and where
I hope to provoke a bit broader discussion: "What's next?"

Until recently for most developers klibc was not much more than a cool
idea, but now we have the first incarnation and now we have to do a
reality check of how it solves our problems. To say it drastically the
current patch set as it is does not solve a single real problem yet, it
only moves them from the kernel to kinit, which may be the first step but
where to?

So what problems are we going to solve now and how? The amount of
discussion so far is not exactly encouraging. If nobody cares, then there
don't seem to be any real problems, so why should it be merged at all? Are
shiny new features more important than functionality?

So anyone who likes to see klibc merged, because it will solve some kind
of problem for him, please speak up now. Without this information it's
hard to judge whether we're going to solve the right problems.

Peter, it would really help if you describe your own plans, how you want
to go forward with it, otherwise it leaves a huge amount of uncertainty
and since this is a rather big change, I think it's a real good idea to
reduce this uncertainty, so we know what to expect and everyone can better
evaluate how these changes will effect him. Right now these patches are
devoid of any documentation, which make it hard for everyone to judge them
(and what is IMO the main reason for the current uncomfortable silence).

Feel free to flame me now for making it so difficult, but I'm convinced
it's better for everyone to make this step (even if it's the right one)
with more information than we have right now...

bye, Roman
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-06-27 15:15    [W:0.353 / U:4.036 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site