World Domination 201: A review

Eric S. Raymond and Rob Landley have written an interesting paper called "World Domination 201". The main idea of this paper is that the entrance of 64-bit processors will force a new operating system to be adopted, which provides a unique opportunity for Linux to become the dominate operating system.

Their conclusion is based on this theory: An operating system will become obsolete when low-end computers are sold with more memory than the operating system can support.

Here is how this transition has happened before:

8-bit processors
  • Dates: 1975-1984 (9 years)
  • Supported Memory: 64 kilobytes
  • Dominate Operating System: BASIC
16-bit processors
  • Dates: 1981-1990 (9 years)
  • Supported Memory: 1 megabyte
  • Dominate Operating System: DOS
32-bit processors
  • Dates: 1987-2008 (21 years)
  • Supported Memory: 4 gigabytes
  • Dominate Operating System: Windows
64-bit processors
  • Dates: 2008-???
  • Supported Memory: 1 terabyte
  • Dominate Operating System: Linux, OS X, or Windows Vista
Historically, the transition to the new operating system occurs around three years after the new hardware was introduced. Since 64-bit processors were first introduced in 2005, this means that the new 64-bit OS will be determined by the end of 2008.

They list these factors as requirements for Linux to succeed:
  • Drivers for all major existing hardware
    • "When it comes to crossing the 32- to 64-bit divide, device driver support is where Linux has its biggest practical advantage over both Microsoft and Apple."

  • 32-bit legacy platform emulation
    • "Linux needs a Wine 1.0 release, installed and preconfigured on desktop distributions."

  • Surviving the killer app
    • "As of yet, there is no killer app for Linux, nor for 64-bit hardware."

  • Enabling preinstalls
    • "To attract enough non-technical end users to make the hardware vendors care about us, we need Linux to come preinstalled on PCs in a configuration that just works."

  • Support for all major multimedia formats
    • "Idealism about open formats will not solve our multimedia problem in time; in fact, getting stuck on either belief in the technical superiority of open source or free-software purism guarantees we will lose."
The authors spend some time exploring the solutions to that last point. They describe six possible approaches to dealing with proprietary codecs:

  1. Do without.

  2. Unload the problem on individual users.

  3. Reverse-engineer all codecs for which deployment is legally possible (e.g. not blocked by patents or the DMCA).

  4. Press for delivery in open formats.

  5. Get closed source binaries that are "free as in beer".

  6. Pay to license codecs, per-copy.

Overall, it is an interesting read. I think the points he make are valid, and the premise of hardware forcing a software upgrade is historically accurate. I believe that Ubuntu is heading the right direction and is poised to be the next major operating system on 64-bit hardware.

Comments

  1. Anonymous1/23/2007 7:06 PM

    I liked your post but there are a few techincal mistakes. Both Intel and AMD 32 bit processors can address 64gb of memory using PAE (just like 16bit processor could address 1 meg).
    I worte a little response and would love to hear your comments.

    ReplyDelete
  2. Anonymous2/11/2007 1:09 AM

    The 8 bit systems had "bank switching". DOS had expanded/extended/extruded memory. And 32 bit systems have PAE.

    And in each case, this hasn't extended the lifespan of the old stuff significantly, because as long as you have to rewrite the software to take advantage of a new more-memory extension API, you might as well just bite the bullet and rewrite it for the new memory model entirely.

    - Rob Landley

    ReplyDelete
  3. Anonymous2/23/2007 6:42 PM

    PAE does not require a rewrite of the software as long as the OS does. Windows XP 32bit does support PAE. I do see people switching to 64bit OS but it will not be as dramatic as a switch as 16bit to 32bit.

    ReplyDelete

Post a Comment

Popular posts from this blog

Using the Cisco console in Linux

Image
Introduction People who work with Cisco network equipment need to be able to connect to the console port on their devices. In Windows, you can simply fire up HyperTerminal to get basic access to your devices. If you are using Linux, then you need to know how this can be done with an application called Minicom . Hardware First, you are going to need a Cisco console cable , a Cisco device, and a computer. If your computer has a serial port , then you can use the standard console cable that comes with every Cisco device. If you do not have a serial port (like most new laptops), then you need to purchase a USB to Serial adapter that supports Linux. This device will allow you to use the standard Cisco cable, which has a serial port on one end. Install Minicom You can easily install Minicom by using "System > Administration > Synaptic Package Manager". Search for "minicom" and choose to install the package. Click "Apply" and Minicom should be insta...
Read more

Linux NIC teaming recommendations

Image
Introduction In my job as a network engineer, I am constantly looking for ways to increase the availability of the network. This is especially true in the data center, where services are expected to always be available. One of the ways to increase the network availability of a server is by using multiple network interfaces. This technique has many different names, but I am just going to call it NIC teaming. Purpose of NIC Teaming NIC teaming increases network availability by removing single-points-of-failure (SPOF). These SPOFs are components that will cause a service outage if they become unavailable. If we consider a single network connection from your server to your switch, we can identify quite a few SPOFs: Server NIC failure Network cable failure (such as being cut or unplugged) Network switch failure (such as a planned firmware upgrade or unplanned outage) Methods of NIC Teaming The reason I am writing this blog is to help people understand the different options for NIC team...
Read more

What it takes to make Ubuntu ready for use

I recently installed Ubuntu 6.10 on a new PC at work. In this post I will document all the steps I had to perform to get it ready for everyday use. Each step is assigned a level of difficulty, which I define below: Very Easy Step can be completed without using the command prompt Intuitive to complete Easy Step can be completed without using the command prompt May require searching to find the right place to make the change Medium Requires a single command to be entered at the command prompt Requires searching internet resources to find the solution Hard Requires multiple commands to be entered at the command prompt Requires searching internet resources to find the solution Very Hard Requires multiple commands to be entered at the command prompt Requires searching internet resources to find the solution Requires the user to manually edit a configuration file These criteria are quite strict, because I believe that using an operating system should be intuitive, and not require any spec...
Read more