I understand all the kernel-mode cleanups -- moving initializationfrom kernel to user space is a very good thing.

But the question really is: why yet another libc? We already havedietlibc, uclibc, glibc, now klibc... With modern kernel, initramfswill very probably contain quite some programs linked with glibc(modprobe/insmod, mdadm/lvm, etc; I highly suggest putting someminimal text editor like nvi there too, for rescue purposes) --so why not have an option to use whatever libc is available onthe host platform?

In the other words, kinit/ipconfig/nfsmount/etc stuff is ok,no questions. But the libc itself -- what for?

And another related question: why not dietlibc which is alreadyhere, for quite long time?