GNU/Linux Desktop Survival Guide by Graham Williams
Desktop Survival Project Home Preface Advocacy History Distributions Installation Basic Survival Wajig Audio AbiWord APM Backup Bash Booting Cameras CD Chinese ChRoot Clock Commercial Conference Management Configuration CRON CVS Databases DIA Directories Disks Documentation DVD Email Eye of Gnome Evolution File Systems Firewalls Floppy Disks Fonts Ghemical GIMP Glade Gnome GnuCash Gnumeric GQView Graphics Groups HTML Editors ImageMagick Initialisations on Booting Java KDE Kernels Keyboard Konqueror KVM Switch LaTeX Log System Login Magellan Mathematics Memory Modems Mounting Devices MS/Windows Music MySQL Nautilus Networks NFS NT File System OpenOffice.org Oracle Packages Partitions Passwords PDF Photos PPP Presentations Printing Python R Remote Desktops Rsync Samba Scanning Science Security SH File System Sketch Spell SPlus Spruce SSH SUDO Subversion Swap Themes USB Video Virtualization Web Word X XML Sample Installations Troubleshooting Index

Fear, Uncertainty, Doubt

FUD (Fear, Uncertainty, Doubt) was originally defined by Gene Amdahl after he left IBM to found his own company. He used it to describe the fear, uncertainty, and doubt that the IBM sales people were spreading to their customers who might be considering the competitions products. The competition was Amdahl! More recently the term FUD has increasingly become associated with Microsoft, using the tactic to ensure customers stay with their products. Spreading incorrect and unsubstantiated rumours to fuel doubt about a product is the name of the game.

An example of this is a famous case initiated by a company called SCO which attempted to extract ``rent'' from all users of Linux. The company claimed that Linux included code that they owned. Hence, everyone using Linux had to be worried that SCO would soon come after them with substantial financial claims. Having been interviewed by the Australian press on this matter the author of this book become well aware of the effective impact this type of campaign can have on organisations considering a move to GNU/Linux from Microsoft.

In particular, SCO took IBM to court over the matter. The company did not disclose any code publicly, hiding behind the fact that they disclosed it all to a judge and regrettably this limited their ability to disclose it publicly. Fortunately, in February 2005, this Judge Kimball found it incredible that after trash talking IBM in public for two years, SCO has presented no evidence to back up their words:

Viewed against the backdrop of SCO's plethora of public statements concerning IBM's and others' infringement of SCO's purported copyrights to the UNIX software, it is astonishing that SCO has not offered any competent evidence to create a disputed fact regarding whether IBM has infringed SCO's alleged copyrights through IBM's Linux activities.

Fortunately, while this attempt to discredit GNU/Linux was unwelcome, it certainly lead to significant due diligence to ensure there was no risk to GNU/Linux.

Below are some reported statements from Microsoft:

• It has the potential to fragment like Unix did. (Kevin Johnson, Microsoft's group vice-president for worldwide sales, marketing and services, in an interview with BusinessWeek, January 2004.)
• There is a risk that Linux will end up fragmented like the Unix operating system. (Nick McGrath, head of Microsoft's platform strategy, quoted by ZDNet, 2 February 2005.)
• Microsoft CEO Steve Ballmer said, under oath, during Microsoft's antitrust trial, that if he didn't like the judge's decision he'd withdraw Windows from the market. We can't make such threats with GNU/Linux!