On Tue, 14 Apr 2015, Greg Kroah-Hartman wrote: > Yes, it's an unfortunate design, but one that we are all stuck with > (think of it as having to implement code for horrid hardware that you > have to get to work properly.)
Greg, I personally consider this a rather defunct analogy. Broken hardware comes from "outter space" we just have to live with somehow, and eventually try to gradually improve by working with vendors (and you yourself have of course made huge improvements in this very area). Linux userspace is coming, well, from Linux developers. The sole fact that someone wrote a daemon that runs on Linux seems like a very poor justification for sucking the daemon into kernel "because we have to live with it". Userspace has to live with it somehow (and eventually fix itself if necessary), yes. Why should kernel just contribute to this "unfortunate design" if it really isn't, in any way, obliged or forced to do so? Thanks, -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
