Linked by Thom Holwerda on Fri 30th May 2008 14:49 UTC
Windows We have learnt quite a lot about Windows 7 this week, and one of the things was that Windows 7 would not get a new kernel. The call for a new kernel has been made a few times on the internet, but anyone with a bit more insight into Windows' kernel knows that there is absolutely no need to write a new kernel for Windows - the problems with Windows lie in userland, not kernelland. While the authenticity of the Shipping Seven blog is not undisputed, the blogger makes some very excellent points regarding the kernel matter.
Permalink for comment 316433
To read all comments associated with this story, please click here.
RE[7]: Comment by FunkyELF
by ashigabou on Sun 1st Jun 2008 05:34 UTC in reply to "RE[6]: Comment by FunkyELF"
ashigabou
Member since:
2005-11-11

But should the explorer hang as well due to that particular misbehaving driver?


Is the driver is misbehaving, the kernel cannot do much about it most of the time (in so called monolithic kernels, at least). If the misbehaving driver for example corrupts any data structure used by the kernel, you are screwed.

The problem really is misbehaving drivers, and the fact that a lot of things used to run in kernel space in windows did not help, as well as the big number of crappy drivers. Fortunately, with Vista, it looks like they have put a lot of things in userland, where it belongs (that's what they pretend, at least, I have not checked it, I am not interested in windows). Less code in kernel space certainly means more reliability here.

Reply Parent Bookmark Score: 1