To read all comments associated with this story, please click here.
Typically, it is only X that crashes. And when X crashes, it will always take your whole X session with it. And programs connected to the X server from elsewhere will happily die with SIGPIPE or whatever as they lose their connection.
Apart from that, yes, this is a great and important step for the Linux based desktop.
Ah, SIGPIPE, bane of my job. My boss likes to solve all problems by popening onto external applications (from compiled C code)... which means that I get to spend a lot of time worrying about catching and handling SIGPIPE.
That and, if the graphics server or graphics driver dies, I think it's reasonable for the whole session and all running apps to go down. It's certainly not surprising. At least for me, the problem is that X goes down a lot, and isn't really stable, high-performance or bug- and glitch-free while it's up!
Edited 2009-09-10 22:48 UTC




Member since:
2007-02-17
Kernel Mode Setting is important because having that level of support in the kernel apparently means that the rest of the X graphics stack can be written to run in userland (i.e. it can run as a usermode program, it won't require root priveleges any more). This is a great improvement from a security perspective.
In turn this may also possibly allow X and/or the driver to crash, and be re-started, without crashing any application program.