If it doesn’t, then somebody needs to fix it.Īctually, in the case of an incomplete, in-kernel, open source hardware driver, with Linux you’d be justified in (mostly) blaming the kernel developers. Btu in the end, if stuff doesn’t work, then the reason really doesn’t matter as far as in end user is concerned. He also runs my Slackware based operating system at home and it serves primarily as a virtualisation base to run all kinds of Windows releases on, since XP proved too unstable a few years ago.įrankly, I believe it is the fault of the hardware vendors in both cases. Having had a discussion on this with a relative who has been an MCSE since NT 4.0 but who has also worked with OpenVMS (VAX/Alpha), HP-UX and Solaris, he came to the same conclusion. As long as the kernel itself and all drivers are not tested together crashes may happen. I am certain the NT kernel would be a lot more stable if Microsoft adopted the same policy of developing and maintaining drivers alongside the core of the kernel itself. The way drivers are included in the Linux kernel means that although not all drivers for everything under sun are included, many are and they are tested together constantly so conflicts between drivers are resolved much easier and faster because all drivers can be modified at once if necessary.

This isn’t an attack on either but someone has to take responsibility and must be held accountable.Īlthough I don’t have any experience with Vista apart from a quick test of Beta 2 in VMware more than a year ago I do have experience with various XP SP2 installations where various certified drivers either included in Windows or from hardware vendors are conflicting up to the point where the system is too unstable for use just after a fresh install. I doesn’t matter if it’s Microsoft’s or the hardware vendors’ fault. It’s the problem with the drivers because some vendors obviously didn’t notice the release.

Gnucash 2.0