.... As a Windows user I have been flamed
in more Linux mail lists than I have seen Linux users get flamed here, and I
like Linux. ....
I can second that, I once got flamed through every corner of a newsgroup
for reporting a problem and asking for help solving it.
How not to ask for help in a Linux newsgroup
My first error was to suggest that Linux was responsible for the frequent
file system panics I got on my system (for windows users who don't know
what they are: file system panics and kernel panics are Linux's equivalent
of BSOD's, but black instead of blue to make it harder for us to invent
colorful jokes about them).
My second (and bigger) error was to add that it wasn't the hardware,
because windows ran fine on the same machine (dual boot setup).
In the eyes of 49% of the newsgroup, the first error made me a whining
luser without any computer knowledge. Linux is never at fault, it's always
the user who's doing something wrong.
And they didn't have my problem, so it must be either me or my hardware.
In the eyes of the next 49%, my second error (mentioning Windows) combined
with reporting a problem they'd never seen, made me an anti-linux Windoze
advocate whose only intention was to come trolling with lies about the Holy
OS's Infallible Stability. Flames straight out of hell, with a rock/horror
score written by Jim Steinman in the back.
Then I made my biggest error, by replying in kind to those allegations.
A week later, a few unrelated posts to the same newsgroup still got greeted
with goats and flames (GOAT = go away troll).
The remaining 2% recognized and correctly diagnosed the symptoms - a CD-R
drive that wasn't compatible with Linux's ATAPI CD-R support, which was
still experimental at the time, causing a file system panic some time
between 0 and 15 minutes after a read error on a CD.
The suggestion I got from at least two people was to stop being such a
cheapskate and replace that ATAPI CD-R with a SCSI one, then the problem
would go away, and those drives were much better anyway.
The next kernel release fixed it too, but at a somewhat lower cost