Why Many Linux Features Are Actually Ancient Unix Concepts

1. Dual‑booting

Dual‑booting allows a single computer to run two or more operating systems by selecting the desired OS at power‑on. The technique predates Linux and was used on early PC‑Unix systems such as Xenix, on the Amiga (e.g., Amiga 3000UX could boot either Amiga Workbench or a System V‑based Unix by clicking the left or right mouse button), and on many MS‑DOS/Unix combinations.

2. Support for Multiple Architectures

When Linus Torvalds released the first Linux kernel in 1991, it targeted only Intel x86. Because the kernel and most user‑space utilities are written in portable C, any platform with a C compiler can build Linux. This mirrors the Unix transition in the early 1970s when Dennis Ritchie rewrote the kernel from assembly to C, decoupling the OS from a specific hardware design and enabling ports to PDP‑11, VAX, SPARC, ARM, PowerPC, and many other architectures.

3. Interchangeable Shells

The ability to replace the login shell (e.g., Bash, Zsh, Fish) originates from the Multics project, which introduced the concept of a replaceable command interpreter. After Multics, Ken Thompson and Dennis Ritchie incorporated a similar mechanism into Unix, allowing users to specify an alternative /etc/passwd shell field. This design separates the user interface from the kernel and has persisted in Linux, where chsh can change the default shell for any user.

4. Early WSL‑like Compatibility Layers

Microsoft’s Windows Subsystem for Linux (WSL) runs native Linux binaries on Windows. A conceptual predecessor appeared in 1988 when Digital Equipment Corporation (DEC) started the MICA project for the PRISM processor. MICA combined VMS services with a Unix‑style environment, aiming to run Unix applications on a VMS‑based system. Although MICA was cancelled, its lead engineer Dave Cutler later headed the Windows NT project, which shipped a POSIX compatibility subsystem (primarily to satisfy government contract requirements). Subsequent Microsoft offerings—Windows Services for UNIX and the open‑source Cygwin project—extended this compatibility model, providing a Unix‑like user space on Windows.

5. Legal Battles Over Unix Code

In the early 2000s, the SCO Group sued IBM, alleging that Linux contained proprietary Unix code owned by SCO. The case was eventually dismissed, and the Linux community retained the right to use and distribute the contested code. A similar dispute occurred in the early 1990s when AT&T’s Unix System Laboratories claimed copyright over Berkeley Software Distribution (BSD) source files. The settlement required the removal of a small number of AT&T‑owned files from BSD releases, after which BSD continued as a fully open source system.

6. Competition Between Distributions and Unix Variants

Modern debates over the “best” Linux distribution echo the historic rivalry between AT&T’s System V and the University of California, Berkeley’s BSD in the 1980s. The “Unix wars” led to attempts at unification (e.g., the creation of the Open Software Foundation and Unix International). Ultimately, the market coalesced around standards such as POSIX, while Linux later emerged as the dominant open‑source Unix‑like system.

7. The “Unix Desktop Year”

Efforts to make Unix‑like systems usable by non‑technical users date back to a 1989 PBS documentary that showcased desktop environments from Sun, HP, and Apple’s A/UX. Linux desktop environments (GNOME, KDE, Xfce, etc.) continue this tradition by providing graphical interfaces, application menus, and integrated software stores aimed at mainstream users.

8. Open‑Source Licensing Heritage

Although the GNU Project popularized the term “free software” and introduced copyleft licenses such as the GPL, the practice of sharing source code predates GNU. Early BSD releases used permissive licenses that allowed redistribution and modification, establishing a legal foundation that later projects—including Linux—built upon.