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

Reliability

GNU/Linux is a very stable operating system and system crashes are virtually unknown. GNU/Linux, like Unix before it, is designed to be a multi-user, shared system. Simply because one user of the system runs an application that crashes, other users of the same system should not be affected. Also, most GNU/Linux applications have been in open development for many years with many developers working on and looking over the code. Bugs of course are not unknown, but they are usually quickly fixed within GNU/Linux, leading to a very reliable system.

A source-code analysis of the MySQL database, for example, conducted in January 2005, revealed only a few bugs in this open source database which drives many web sites, compared with the number found in commercial code. The analysis was conducted by testing company Coverity. Their analysis found an average of one bug in every 4,000 lines of code-this is at least four times better than is typical with commercial software.