Linked by Thom Holwerda on Fri 30th May 2008 14:49 UTC
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 316232
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2006-03-18
Really? Didn't know the BSOD ran as a user process.
BSOD? What's that? Never seen one with Vista. In fact, I think I saw one in 5 years of working with dozens of XP systems.
Also didn't know that process management was a userland thing either. That must explain why when I tell the OS to kill a process, I have to tell it 15 times before it dies. This explains a lot.
Taskmanager will always kill a process immediately, but will be more likely to result in loss of data. The "End Now" dialog is a bit more conservative, and also invokes the various (slow) crash logging processes. I two wish the "End Now" dialog actually did what it said, but taskmanager is more than adequate.
Why are you telling me this...I don't care if it isn't responding, I'M SHUTTING DOWN you idiot OS!
You shutdown your laptop? I just close the lid, it goes to standby, and then hibernates after few minutes.
As for the "some crap is not responding" - would you prefer the OS terminate applications and lose your data without confirmation? I think I'd rather have depleted battery.
What I cannot understand is why the shutdown process is such a frigging pain - and it has mostly to do with userland programs that pop up interactive dialogs on shutdown. The OS simply can't know what to do in this instance. It'd be nice if most programs were written to simply save themselves to a safe state on shutdown, and address any outstanding issues when the user next starts the program - "When you last shutdown, you were editing this file but didn't save it, do you want to save your changes or revert?"