[Halfmanhalfamazing]

In the Windows world there's no responsibility from a single source for the OS software. While "single source" is a major MS selling point it's not really true. The people responsible for Windows drivers often point fingers at each other. Manufacturers state that it's something else you installed that broke the operating system. Microsoft might help you.. for $129USD or so an hour. Or they might just point out that the driver you're using isn't "certified" by them to work so you'll need to beg the vendor.

Drivers in the Linux kernel have a clear cut maintainer. If the driver is currently available then the maintainer's name is generally stamped right in the source directory along with how to get ahold of someone if you're having trouble. Starting with a search for similar problems usually yields a solution. In extreme cases it may be necessary to send the problem upstream on the LKML (Linux Kernel Mailing List) for the kernel folks to take a look at and fix if necessary. Even if it isn't their problem, but is instead an issue with poorly implemented hardware, a politely worded question will usually yield prospective solutions.

The episode with the firewire card just reminded me of why I switched to Linux all those years ago. Long before I started writing about the penguin OS or working as a professional supporting it I had a similar hardware problem. In the end, Linux's hardware support "just worked" and I haven't had any unresolvable problems with it since.

[Michael Goldsberry]

Popcorn thread.

[sigSEGV]

People are always amazed when I plug in new hardware on a Linux box and it just starts working -- no driver download, no confusing dialog boxes to find the driver files, no reboot neccessary...

[FreeReign]

While "single source" is a major MS selling point it's not really true. The people responsible for Windows drivers often point fingers at each other. Manufacturers state that it's something else you installed that broke the operating system. Microsoft might help you.. for $129USD or so an hour. Or they might just point out that the driver you're using isn't "certified" by them to work so you'll need to beg the vendor. Drivers in the Linux kernel have a clear cut maintainer. If the driver is currently available then the maintainer's name is generally stamped right in the source directory along with how to get ahold of someone if you're having trouble.

False comparison.

On Windows, the vendor of the H/W is responsible for the drivers. On Linux, it's the maintainer.

Both the Windows vendor and the Linux maintainer can say that something else that you installed broke the OS.

[ShadowAce]