From: Herbert Xu <[EMAIL PROTECTED]> Date: Fri, 28 Jul 2006 12:22:29 +1000
> I suppose another case in point is IPv4 autoconf which > is *still* in the kernel after all these years. At least in that case, H. Peter Anvin has put together a klibc equivalent. Klibc is one possible way out of this quagmire. But we have to wait until everyone is able to convert over to it. This isn't like changing the module interfaces and APIs, for example, it is a much larger change from the userland perspective. And it took a long time for the module bits to propagate fully, which as I said was a less drastic case. And klibc is only really good for bootup stuff and loading initial drivers. It probably cannot be applied to things like ARP and NDISC. IPv4 autoconf works as a good application of klibc because you only need it to run from the initial ramdisk on bootup. > However, to draw an analogy we're kind of stuck in a bog here. So > while we can't extricate ourselves easily, we should attempt to come > up with ways of eventually lifting us out. We should also try to > avoid any actions that'll cause us to sink deeper :) That's why we are very careful when evaluating new protocol implementations that want to be in the kernel. The first question we always ask is "can you do this reasonably in userspace?" - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
