Language Selection

English French German Italian Portuguese Spanish

Infamous Microsoft FUD Campaigns Against Linux

Filed under

From the buggy-yet-popular Windows 95 to the god-knows-what-it-is and upcoming Windows 8, Microsoft has come a long way. Unlike the 90’s, they aren’t just making computers, today they manufacture almost anything your tech-savvy mind can dream of. But after all these years, what hasn’t changed is the fact that Microsoft is still a company full of uptight nerds who think that attacking their competitors is what makes them no 1. Microsoft’s long war against Linux, Android and all things related to Free and Open Source Software (FOSS) is something that can’t be ignored anymore.

Here is a look at the history of Microsoft's infamous FUD (Fear, uncertainty and doubt) campaigns against Linux and FOSS:

Microsoft's first FUD

Microsoft initially had no big competitors. Everything was peachy in the rapidly-growing Gatesland. From office desktops to giant servers, Windows was having a somewhat faddish influence on the computer-curios crowd.

Rest here

Do we need counter-FUD against Microsoft?

The article seems to be as full of errors as any Microsoft FUD. Unix and BSD flavors were available on Intel microprocessors prior to Windows 95, as were MacIntosh 68000 processor and PowerPC computers. DOS and Windows 3.x clients were used on Novell Netware, IBM Minicomputer, and Unix networks well before Windows 95, and Windows networks with peer-to-peer networking were working under DOS 4/5/6.

Unfortunately, the only market share where Linux has been able to make inroads is the *nix market.


"Unlike the 90’s, they aren’t just making computers"

Um... when did Microsoft EVER make a computer?

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Security Leftovers

  • Friday's security updates
  • Researchers poke hole in custom crypto built for Amazon Web Services
    Underscoring just how hard it is to design secure cryptographic software, academic researchers recently uncovered a potentially serious weakness in an early version of the code library protecting Amazon Web Services. Ironically, s2n, as Amazon's transport layer security implementation is called, was intended to be a simpler, more secure way to encrypt and authenticate Web sessions. Where the OpenSSL library requires more than 70,000 lines of code to execute the highly complex TLS standard, s2n—short for signal to noise—has just 6,000 lines. Amazon hailed the brevity as a key security feature when unveiling s2n in June. What's more, Amazon said the new code had already passed three external security evaluations and penetration tests.
  • Social engineering: hacker tricks that make recipients click
    Social engineering is one of the most powerful tools in the hacker's arsenal and it generally plays a part in most of the major security breaches we hear about today. However, there is a common misconception around the role social engineering plays in attacks.
  • Judge Gives Preliminary Approval to $8 Million Settlement Over Sony Hack
    Sony agreed to reimburse employees up to $10,000 apiece for identity-theft losses
  • Cyber Monday: it's the most wonderful time of year for cyber-attackers
    Malicious attacks on shoppers increased 40% on Cyber Monday in 2013 and 2014, according to, an anti-malware and spyware company, compared to the average number of attacks on days during the month prior. Other cybersecurity software providers have identified the December holiday shopping season as the most dangerous time of year to make online purchases. “The attackers know that there are more people online, so there will be more attacks,” said Christopher Budd, Trend Micro’s global threat communications manager. “Cyber Monday is not a one-day thing, it’s the beginning of a sustained focus on attacks that go after people in the holiday shopping season.”

Openwashing (Fake FOSS)

Android Leftovers

Slackware Live Edition – Beta 2

  • Slackware Live Edition – Beta 2
    Thanks for all the valuable feedback on the first public beta of my Slackware Live Edition. It allowed me to fix quite a few bugs in the Live scripts (thanks again!), add new functionality (requested by you or from my own TODO) and I took the opportunity to fix the packages in my Plasma 5 repository so that its Live Edition should actually work now.
  • Updated multilib packages for -current
  • (Hopefully) final recompilations for KDE 5_15.11
    There was still some work to do about my Plasma 5 package repository. The recent updates in slackware-current broke several packages that were still linking to older (and no longer present) libraries which were part of the icu4c and udev packages.