> The only real reason you would want to run something outside of the
> kernel in regular operation is if the license prevents you from
> putting it in the kernel (stay tuned ;).  Well, that or you have a
> strange fetish for wanting things to run slower than they can...

...or the code is known to be buggy and you'd rather just have to
restart a user process than have to reboot, even if it involves a
performance lose.  (Yes, the world being what it is, sometimes
non-developers have to run known-buggy code.)

Or, to tie this to another thread, you want to be able to constrain
what the code can do, by forcing its interaction with the rest of the
kernel into a comparatively narrow and well-controlled channel, and
then applying constraints to, snooping on, or interposing into that
channel.

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse@rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B