Berkeley Software Distribution

When Ken Thompson, Dennis Ritchie, and Rudd Canaday created UNICS at Purdue University in 1969, they had no idea they were launching a lineage that would give birth to one of the most influential operating system families in computing history. UNICS was renamed UNIX two years later, and as early as 1973-1974, the system saw its first branches with PWB/UNIX and MERT. While PWB/UNIX would evolve into System III, MERT disappeared from the radar.

The true BSD adventure began on March 9, 1978, in the offices of the Computer Systems Research Group at the University of California, Berkeley. This first version of BSD was modest, but versions 2 and 3 marked a turning point. DEC’s 32-bit VAX machines gradually replaced the aging PDP-11s, and BSD adapted to this technological transition. The developers integrated Thompson’s reworked Pascal compiler, the vi editor that would become legendary, and the C shell that was a game-changer for system administrators.

The story might have ended there without DARPA’s providential intervention. Bob Fabry secured an 18-month funding that transformed BSD 3 into an innovation laboratory. Virtual memory made its appearance, accompanied by demand paging and sophisticated page replacement algorithms. These improvements laid the groundwork for BSD 4, which introduced the ARPANET protocol—the ancestor of TCP/IP—and redesigned memory management. The termcap database advanced terminal management, while device support gained robustness.

Jim Kulp contributed to BSD 4.1 with job control, but it was especially the automatic hardware detection that transformed users’ lives. Gone were the tedious kernel recompilations with every configuration change: the system now recognized and configured devices automatically at boot time. A kernel could now run on different machines without human intervention.

The year 1983 marked the pinnacle with BSD 4.2. Bill Joy and Kirk McKusick delivered their masterpiece with the Berkeley Fast File System, which far surpassed traditional UFS in terms of performance and disk space utilization. Signals revolutionized inter-process communication, IPC structured complex exchanges, and TCP/IP established itself as the networking standard. These innovations inspired a generation of systems: SunOS 1.2, Ultrix-II, Mach, and MIPS OS drew directly from this technological goldmine.

BSD 4.3 was released in 1986 with the mission of consolidating achievements and refining TCP/IP. The system reached remarkable technical maturity, but the commercial aspect entered the picture. In 1990, BSDi launched BSD/386 based on BSD Net/2 code. This commercial version positioned itself as a credible alternative to AT&T’s System V, with a compelling argument: a more affordable price. However, the sword of Damocles of AT&T’s license still hung over BSD.

The bombshell came in 1992 when AT&T took BSDi to court for trademark violation and false advertising. After an initial failure, AT&T came back in 1993, this time against both BSDi and the University of California. The charge: unauthorized distribution of proprietary code. The situation became more complex when AT&T sold USL and UNIX rights to Novell. It would take until February 4, 1994, to see the birth of 4.4BSD Lite, purged of all elements under AT&T license.

Meanwhile, Bill Jolitz was working behind the scenes on 386BSD. His approach differed: rather than negotiating with lawyers, he developed alternatives to the problematic components. This approach resulted in a completely free version of BSD, freed from the legal constraints that had hindered its development. Distributions temporarily slowed, but this technical liberation constituted a strategic victory for free software.

The following years saw several branches emerge: NetBSD was born from BSD Net/2 code, FreeBSD extended the legacy of 386BSD, DragonFlyBSD later split from FreeBSD, and Apple discreetly integrated FreeBSD elements into macOS X’s hybrid Mach/BSD kernel.

BSD’s technical legacy spans decades. The FFS file system still inspires contemporary developers. Berkeley’s TCP/IP stack remains a reference for understanding network protocols. Job control and automatic hardware detection are now part of the standard UNIX landscape. But beyond these technical contributions, BSD inaugurated an unprecedented development model: collaboration between university and industry, collective code improvement, sharing of innovations.

Its permissive license stands in contrast to more restrictive approaches. This openness favored the adoption of BSD code in commercial projects, creating an ecosystem where academic research and industrial development mutually enriched each other. macOS perfectly illustrates this symbiosis: a commercial system that integrates and values free components.

BSD’s fragmentation into multiple variants—FreeBSD, NetBSD, OpenBSD—paradoxically reflects its vitality. Each branch explores specific territory: NetBSD focuses on universal portability, OpenBSD prioritizes absolute security, DragonFlyBSD rethinks multiprocessor architectures. This diversity enriches the ecosystem rather than weakening it.

In the grand history of computing, BSD embodies the transmission of technical knowledge across generations of developers. The system traveled from university to industry, from research to critical applications, without losing its soul or intrinsic qualities.