Once again, do in kernel space what *makes sense* to do in kernel
space. In this case, static serving with a policy from user space
makes pretty good sense to do in kernel space (like knfsd vs unfsd)
whereas it would be idiotic to do dynamic serving or set policy there.
Besides, it's (a) optional and (b) localized (doesn't mess around with
any other kernel code). You wouldn't want it in a machine that wasn't
a web server as its main function, that's for sure.
-hpa
-- "The user's computer downloads the ActiveX code and simulates a 'Blue Screen' crash, a generally benign event most users are familiar with and that would not necessarily arouse suspicions." -- Security exploit description on http://www.zks.net/p3/how.asp- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/