SSD Nodes Learn Hosting plans →
Guides Matt ConnorBy Matt Connor

History of BSD: Berkeley to FreeBSD and OpenBSD

How Berkeley's CSRG built BSD, what the 1992 USL lawsuit changed, how FreeBSD, NetBSD, OpenBSD and DragonFly split, and which BSD code runs on Linux today.

The history of BSD in one paragraph

The history of BSD starts with a research group at the University of California, Berkeley, that spent the 1980s extending AT&T's Unix and then replacing the AT&T code inside it. A lawsuit over that code ran from 1992 to early 1994. When it ended, the freed code base, 4.4BSD-Lite, became the base for FreeBSD and NetBSD, and later for OpenBSD and DragonFly BSD. Some Berkeley work also reached ordinary Linux servers, even though Linux contains no BSD kernel.

This account picks up where the history of Unix from Bell Labs to Linux leaves the Berkeley thread, so it does not retell the Bell Labs years. The main source is "Twenty Years of Berkeley Unix" (1999), the standard history by Marshall Kirk McKusick, who implemented 4.2BSD's new file system. Project dates come from each project's own release pages. Where two primary sources disagree, the text says so.

Who built BSD at Berkeley?

The name came first, from a bundle of software. McKusick writes that "early in 1977, Joy put together the 'Berkeley Software Distribution.'" By mid-1978 the bundle needed an update, and Bill Joy produced the "Second Berkeley Software Distribution," a name quickly shortened to 2BSD.

The first full system for the VAX computer came next. In December 1979 Joy shipped the first of nearly a hundred copies of 3BSD, the first VAX distribution from Berkeley.

The group that carried BSD for the next fifteen years formed in 1980. DARPA (the Defense Advanced Research Projects Agency) wanted one common operating system across its research sites, and its planners chose Unix. Berkeley won an 18-month contract with DARPA that began in April 1980. Bob Fabry set up an organisation to do the work and named it the Computer Systems Research Group, or CSRG.

The DARPA releases followed quickly. 4BSD came out in October 1980 and 4.1BSD in June 1981. The next release did not become 5BSD. AT&T objected that the name could be confused with its own System V, so Berkeley kept the 4.x numbering from then on.

4.2BSD: where sockets and the TCP/IP stack came from

4.2BSD, released in August 1983, introduced the socket interface that later spread far beyond BSD. McKusick lists its goals as a faster file system, flexible interprocess communication facilities, and integrated networking for the ARPAnet, the research network that grew into the internet.

The networking code has a more mixed origin than the popular story. TCP/IP (Transmission Control Protocol and Internet Protocol) was not born at Berkeley. Rob Gurwitz of BBN (Bolt Beranek and Newman) released an early implementation of the protocols to Berkeley, and Joy integrated it into the system and tuned its performance. In 1985 a dispute with BBN arose over which code the next release should carry. DARPA's final decision was that 4.3BSD would keep the Berkeley code base.

The programming interface is the part that travelled furthest. The Linux manual page for socket(2) records the call's history as "POSIX.1-2001, 4.2BSD." It also says the interface is generally portable to non-BSD systems that support clones of the BSD socket layer, including System V variants. In practice, socket code written for one Unix-like system can usually be moved to another.

4.3BSD followed in June 1986. Two interim releases came after it: 4.3BSD-Tahoe in June 1988, and the licensed 4.3BSD-Reno in early 1990.

Net/1 and Net/2: the first freely redistributable BSD code

Before June 1989, no Berkeley release could be passed on freely, because the system still mixed Berkeley's code with AT&T's. Berkeley's answer was to split out the code it had written itself.

Networking Release 1, or Net/1, came out in June 1989. It held the networking code that started at Berkeley, plus supporting utilities, and McKusick calls it "the first freely-redistributable code from Berkeley." Berkeley charged $1,000 for a tape, but anyone who had a copy was free to give it to someone else. The conditions were short: keep the copyright notices in the source, and credit Berkeley in the documentation.

Networking Release 2, or Net/2, began shipping in June 1991 on the same terms and at the same price. McKusick calls it a "greatly expanded" release. Six kernel files were left out, because they were still contaminated by AT&T code.

386BSD and BSDI: BSD on the PC

Net/2 was missing only six files, and two groups filled the gap within months.

Bill Jolitz wrote replacements for the six missing files within six months of Net/2's release. The FreeBSD project's article "Explaining BSD" says William F. Jolitz released the result in early 1992 as 386BSD (McKusick spells it 386/BSD). It was a fully compiled, bootable system for PCs with an Intel 386 processor, and it was free to download by anonymous FTP (file transfer protocol).

A company built a commercial system from the same base. BSDI (Berkeley Software Design, Inc.) began selling its system, with both source and binaries, in January 1992 for $995. BSDI became the first target of the lawsuit.

What was the USL v. BSDi lawsuit about?

The lawsuit was brought by USL (Unix System Laboratories), AT&T's Unix business at the time. The FreeBSD project's article simply says that AT&T sued BSDI. USL's first complaint, dated 20 April 1992 in the federal court for New Jersey, named only BSDI. It was not a copyright case at that stage. It pleaded trademark infringement, false advertising and unfair competition under the Lanham Act, the United States federal trademark law.

The case widened in the summer. The First Amended Complaint of 24 July 1992 added the Regents of the University of California as defendants. It also added counts for copyright infringement, trade-secret misappropriation and breach of contract. From this point the question was whether Berkeley's freely distributed code still contained USL's property.

In December 1992, Judge Dickinson R. Debevoise of the United States District Court in New Jersey heard the arguments on the request for an injunction. McKusick writes that about six weeks later the judge denied the injunction and threw out all but two of the complaints. The University then filed its own case in California state court.

How did the lawsuit end?

The case ended in a settlement. By then Novell owned USL. A press release that Keith Bostic posted on 6 February 1994 describes Novell as the company "which recently acquired USL." McKusick dates the settlement to January 1994, so the safe statement is that it was reached and announced in early 1994.

The terms were small compared with the size of the fight. Out of the roughly 18,000 files in Net/2, three were removed and a number of other files received minor changes. The University also agreed to add USL copyright notices to about 70 files, and those files stayed freely redistributable. The press release states the result plainly: "4.4 BSD-Lite will not require a license from nor payment of royalties to USL."

The free release came in June 1994 as 4.4BSD-Lite, and USL agreed not to sue anyone who used it as a base. A full version, 4.4BSD-Encumbered, shipped at the same time for sites that still held a USL source licence. One last update, 4.4BSD-Lite Release 2, followed in June 1995. After it, the CSRG was disbanded. Berkeley's own BSD work ended there, and the open projects carried it on.

Did the lawsuit give Linux its early lead?

This question is often answered with more confidence than the record supports. The dates are clear:

  • Net/2 began shipping in June 1991.
  • Linus Torvalds announced his hobby kernel on the comp.os.minix newsgroup on 25 August 1991.
  • BSDI went on sale in January 1992, and 386BSD was released in early 1992.
  • USL's first complaint is dated 20 April 1992.
  • The settlement was reached in early 1994.
  • Linux 1.0 appeared in March 1994. The files on kernel.org are dated 13 and 14 March 1994.
  • 4.4BSD-Lite, the clean base for free BSD on the PC, came out in June 1994.

So Linux began before the suit, and the suit hung over BSD on the PC for most of the time in which Linux grew to 1.0. Those dates do not prove that the suit caused Linux's lead. Other factors also shaped Linux's growth, and the record checked here does not measure them. The causal effect is still debated, and this account does not settle it. The kernel side of the story is in the Linux kernel history timeline.

How NetBSD and FreeBSD split from 386BSD

Users of 386BSD shared their fixes as unofficial patches, and two projects formed around it in 1993. The FreeBSD article says both "split off" from 386BSD that year.

NetBSD came first. McKusick writes that within a few months of the 386/BSD release, a group of its users formed the NetBSD group. The NetBSD project names its founders as Chris Demetriou, Theo de Raadt, Adam Glass and Charles M. Hannum. NetBSD 0.8 was released on 20 April 1993 and NetBSD 1.0 on 26 October 1994. The project says its original focus was "quality and architecture independence," and today it describes a portable system that runs on many hardware platforms.

FreeBSD formed a few months after NetBSD. The FreeBSD Handbook says the project began in early 1993, partly as the idea of the last three coordinators of the Unofficial 386BSD Patchkit: Nate Williams, Rod Grimes and Jordan Hubbard. FreeBSD 1.0 was the first CD-ROM distribution. The Handbook dates it to December 1993, while the project's release list says November 1993, so "late 1993" is the accurate summary.

The settlement hit FreeBSD directly, because FreeBSD 1.x was a Net/2 based product. The Handbook says the project was given until the end of July 1994 to stop shipping it, with one last release allowed before the deadline: a bug-fix update to FreeBSD 1.1.5, the final release of the 1.x line. FreeBSD then rebuilt itself "from a completely new and rather incomplete set of 4.4BSD-Lite bits." The Handbook says the move took until November 1994 and that FreeBSD 2.0 came out in December 1994. The release list puts 2.0 in November 1994.

FreeBSD describes its own aim as "high performance and ease of use by end users," and calls itself a favourite of web content providers. As of November 2026 the current production release is FreeBSD 15.1, released on 16 June 2026, with an end-of-life date of 31 March 2027. A setup guide for that release line is in running a FreeBSD 15 server.

OpenBSD: correctness and cryptography first

OpenBSD's origin is usually told as a fork of NetBSD. The OpenBSD pages read for this account do not tell that story directly. They describe OpenBSD as "a freely available, multi-platform 4.4BSD-based UNIX-like operating system." The primary record does show two links to NetBSD. Theo de Raadt was one of NetBSD's four founders, and OpenBSD's own pages compare its hardware ports with NetBSD's, listing "architecture-specific enhancements relative to NetBSD." The earliest date found in the project's own pages is the CVS (Concurrent Versions System) import of its source tree, at 08:37:01 GMT on 18 October 1995.

OpenBSD states its priorities on its front page: "portability, standardization, correctness, proactive security and integrated cryptography." Its licence policy is stricter than most. The goals page says "ISC or Berkeley style licences are preferred, the GPL is not acceptable when adding new code, NDAs are never acceptable." Under that policy, new OpenBSD code carries licences that allow reuse in other systems, closed ones included.

As of November 2026 the current release is OpenBSD 8.0, released on 20 October 2026, which the project counts as its 61st release.

DragonFly BSD: the fork from FreeBSD 4.8

The youngest major branch split from FreeBSD, not from 386BSD. DragonFly BSD was forked from FreeBSD 4.8 in June 2003 by Matthew Dillon. The project says its goal at the start was native clustering support in the kernel, and it describes a kernel rewritten with extreme SMP (symmetric multiprocessing) performance as a goal. Its own file system, HAMMER, first shipped in July 2008 with DragonFly 2.0. When checked in November 2026, the project's releases page listed 6.4.2, from 9 May 2025, as its newest release.

What each branch optimised for

The four projects took the same 4.4BSD-Lite inheritance in different directions:

  • NetBSD: portability. Its founding focus was quality and architecture independence, and it runs on many hardware platforms.
  • FreeBSD: performance and ease of use. The project calls itself a favourite of web content providers.
  • OpenBSD: correctness and proactive security, with cryptography built in and a strict permissive-licence policy.
  • DragonFly BSD: multiprocessor performance and clustering, with its own HAMMER file system.

A server-side comparison of FreeBSD and Linux today is in Linux vs FreeBSD as a server operating system.

What reached an ordinary Linux VPS anyway

A Linux VPS runs no BSD kernel. Several BSD-born pieces reach it anyway, through an API, a program, a file system or a licence.

The BSD sockets API

The socket interface from 4.2BSD is the way Linux programs talk to the network. The Linux socket(2) manual page cites 4.2BSD in its HISTORY section, as quoted above. Network servers on a Linux VPS open their listening ports through this interface, so the shape of network code on that box goes back to Berkeley in 1983.

OpenSSH from OpenBSD

OpenSSH, the SSH server that Linux server images commonly use for remote logins, came from OpenBSD. The OpenSSH project says it is a derivative of the original free ssh 1.2.12 release from Tatu Ylönen, which OpenBSD's 2.6 release notes call "the last with a free license." OpenSSH 1.2.2 shipped with OpenBSD 2.6 on 1 December 1999. A few developers of the OpenBSD project still develop it under a BSD-style licence. A separate portability team maintains Portable OpenSSH for other systems, including Linux. As of November 2026 the newest releases are OpenSSH 10.6 (6 October 2026) and Portable OpenSSH 10.6p2 (5 November 2026).

Any Linux admin can see the lineage on their own server:

ssh -V

The output starts with OpenSSH_ and a version number. On Linux the number carries a p suffix, which marks a Portable release rather than the OpenBSD original. The longer story of the protocol is in the history of SSH from Telnet to OpenSSH.

pf, and where its influence actually reached

pf (packet filter) first appeared in OpenBSD 3.0, released on 1 December 2001. Daniel Hartmeier originally developed it, and it has been part of OpenBSD's GENERIC kernel since that release. The 3.0 release notes describe "a new packet filter, PF, featuring NAT capabilities," NAT meaning network address translation.

Its documented spread is on the BSD side. The FreeBSD Handbook says "since FreeBSD 5.3, a ported version of OpenBSD's PF firewall has been included as an integrated part of the base system." This account found no primary source showing that pf shaped the firewall tools of Linux, so it makes no such claim. On a Linux VPS, pf's influence is indirect at most.

ZFS, by way of FreeBSD

ZFS was originally designed for Sun Solaris, a story told in the history of Solaris and illumos. The FreeBSD 7.0 announcement of 27 February 2008 lists "experimental support for Sun's ZFS filesystem." Since FreeBSD 13.0, the ZFS implementation in FreeBSD has been provided by OpenZFS, the shared open project. The OpenZFS FAQ says OpenZFS "is available for FreeBSD and all major Linux distributions." So the accurate summary is that FreeBSD and Linux now run the same ZFS code base. It would overstate the record to say that FreeBSD delivered ZFS to Linux. The practical differences are covered in ZFS on FreeBSD and Linux.

The permissive licence in commercial systems

The modern FreeBSD licence is a 2-clause BSD licence. Source copies must keep the copyright notice, the conditions and the disclaimer, and binary copies must reproduce them in the documentation or other materials. The FreeBSD project contrasts this with the GPL (GNU General Public License): "the BSD license is less restrictive: binary-only distributions are allowed." The older 4-clause licence carried a third clause, known as the advertising clause. The SPDX licence list records that clause as rescinded by its author on 22 July 1999.

Two documented commercial uses show what the licence allows. Netflix says its Open Connect Appliance software "includes the FreeBSD operating system and the NGINX web server," and that FreeBSD "was selected for its balance of stability and features." Apple's archived Kernel Programming Guide, last updated in 2013 and written for OS X, says "the BSD layer is based on the BSD kernel, primarily FreeBSD." That guide describes OS X of that era, so it is a historical statement and not a description of current macOS. The wider licensing story is in the history of open source.

Can FreeBSD run on SSD Nodes?

SSD Nodes does not offer FreeBSD images, so a FreeBSD server cannot be rented on this platform. Readers who want the closest Linux equivalent of a BSD feature can start with FreeBSD jails vs Docker containers. Image menus can change, so anyone ordering for a specific operating system should confirm the current image list with SSD Nodes support before buying.

FAQ

Is FreeBSD based on Linux?

No. FreeBSD descends from Berkeley's BSD code. The project began in 1993 from patches to 386BSD, which was built on Berkeley's Net/2 release, and it was rebuilt on 4.4BSD-Lite for FreeBSD 2.0 in late 1994. The Linux kernel was written separately and announced by Linus Torvalds in August 1991. The two systems share standards and many programs, such as OpenSSH, but not a kernel.

Why did AT&T's Unix business sue BSDI and Berkeley?

Unix System Laboratories (USL) first sued BSDI alone. Its complaint, dated 20 April 1992, pleaded trademark infringement, false advertising and unfair competition. The amended complaint of 24 July 1992 added the University of California as a defendant, along with claims of copyright infringement and trade-secret misappropriation. The case settled in early 1994: three of roughly 18,000 Net/2 files were removed, and 4.4BSD-Lite was released free of USL licensing in June 1994.

Which came first, NetBSD or FreeBSD?

NetBSD. Both projects grew out of 386BSD in 1993, but McKusick writes that the FreeBSD group formed a few months after the NetBSD group. NetBSD 0.8 was released on 20 April 1993. FreeBSD 1.0, its first CD-ROM distribution, came out in late 1993 (November in the project's release list, December in the Handbook).

Did OpenSSH come from OpenBSD?

Yes. The OpenSSH project says it is a derivative of Tatu Ylönen's free ssh 1.2.12 release. Its first version, OpenSSH 1.2.2, shipped with OpenBSD 2.6 on 1 December 1999. OpenBSD developers still develop it, and a separate team maintains Portable OpenSSH, the version built for Linux. Running ssh -V on a Linux server shows a version with a p suffix, which marks the portable build.

Can a FreeBSD server be rented from SSD Nodes?

No. SSD Nodes does not offer FreeBSD images. Image menus can change, so anyone who needs a specific operating system should confirm the current image list with SSD Nodes support before ordering.

Was this article useful?

#history#bsd#freebsd#openbsd#netbsd#unix