On Fri, 22 Jan 2010, Frank Ch. Eigler wrote: > > The point is that the intermediate api will allow (and, as the part > you clipped out about utrace-gdbstub said, *already has allowed*) > alternative plausible interfaces that coexist just fine. And my point is that multiple interfaces are BAD. There is one interface we _have_ to have: the traditional ptrace one. That one we can't get away from. "Multiple interfaces" on its own is just confusion with no upside. You need a _reason_ to have other interfaces. They need to have that killer feature. Just being "different" is not a feature at all. > So all this is about *naming* utrace? It was never built "for > tracing", but for (efficient/multiplexed) *control*. That wasn't even > its original name -- one of your lieutenants asked roland to change it > to utrace. No. It's not about naming. It's about the downside of having amorphous interfaces that apparently don't even have rules, and are then used to implement random crap. Yes, the SNL skit about "It's a dessert topping _and_ a floor wax" was funny, but it was funny exactly because it was crazy. The fact that you can do crazy things is not a good thing. You need to find the "goodness" somewhere else, and that's what I'm trying to tell you. You just seem to have trouble listening. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html