BSD: The Silent Force Behind Modern Computing

(The image is AI-generated)

 

 

Ask most people to name an open-source operating system and they will say Linux. BSD, the Berkeley Software Distribution, rarely gets a mention, yet its code runs in places you use every day. Apple's operating systems are built on Darwin, whose kernel includes FreeBSD-derived code. Netflix streams video from servers running FreeBSD. OpenSSH, installed on countless servers, comes from the OpenBSD project.

This article traces where BSD came from, how its three main branches differ today, how it compares with Linux, and which popular claims about it hold up. I checked the original draft against primary sources and corrected what I could not confirm.

Quick summary

  • BSD grew out of Berkeley's modifications to AT&T's Unix. Its 4.2BSD release (1983) carried a TCP/IP stack, the sockets interface and the Fast File System.
  • A lawsuit between AT&T's Unix System Laboratories and BSDi was settled in early 1994 and led to the clean 4.4BSD-Lite release, the base of today's BSDs.
  • The three main branches have different goals: FreeBSD for general server and appliance use, NetBSD for portability, OpenBSD for security and correctness.
  • Current releases: FreeBSD 15.1, OpenBSD 7.9 and NetBSD 11.0.
  • BSD's permissive license lets companies build closed products on it, which is why its code shows up in consoles, network gear and Apple's platforms.
  • In 2026, serious vulnerabilities were found and fixed in both FreeBSD and OpenBSD, which is a useful reminder that no operating system is immune.

Where BSD came from

From Bell Labs to Berkeley

Unix was created at AT&T's Bell Labs by Ken Thompson, Dennis Ritchie and colleagues. The University of California, Berkeley, installed Version 4 Unix on a PDP-11/45 in 1974, under Professor Bob Fabry. Graduate student Bill Joy later began collecting improvements into tapes for other sites.

The first Berkeley Software Distribution, 1BSD, appeared on March 9, 1978. It was an add-on to Sixth Edition Unix, not a full operating system. 3BSD (1979) was the first to stand as a complete system, though it still depended on AT&T's source code.

DARPA pays for networking

In 1980, DARPA funded Berkeley to build a standard Unix platform for its research community. Fabry founded the Computer Systems Research Group (CSRG) around that contract. The result was 4.2BSD in August 1983, which contained a modified version of BBN's early TCP/IP code and McKusick's Fast File System.

One nuance the original draft missed: Berkeley did not write its TCP/IP stack from nothing. It started from BBN's implementation, and DARPA later judged the Berkeley version superior. The CSRG authors also report that 4.2BSD shipped more copies in eighteen months than all earlier Berkeley releases combined. The sockets interface introduced in this period is the model most networked operating systems still follow.

The lawsuit that shaped everything

By the early 1990s, Berkeley had released the Networking Releases (Net/1 in 1989, then Net/2) with most of the AT&T code replaced. A company called BSDi built a commercial product on Net/2. In 1992, AT&T's Unix System Laboratories sued BSDi and the University of California, claiming copyright and trade-secret violations.

The case settled in early 1994, after Novell had bought USL. The outcome, as summarized on Wikipedia, was mild for Berkeley: of roughly 18,000 files, only three had to be removed and about 70 changed. Berkeley then released 4.4BSD-Lite in June 1994, followed by Lite Release 2 in 1995, and the CSRG was dissolved.

Analysis: The same Wikipedia summary argues that the legal cloud slowed free BSD systems for nearly two years and helped Linux gain support. That is a widely held view, but it is an interpretation, not a measured fact.

The BSD family today

Every living BSD descends from 4.4BSD-Lite, directly or through other projects. FreeBSD's own history notes that FreeBSD 2.0, released in November 1994, was its first version with no AT&T code.

FreeBSD

FreeBSD is the most widely used of the three. It keeps the kernel, userland tools, build system and documentation in one source tree. It is common in servers, firewalls, storage appliances and embedded products. Software installs either as binary packages with pkg or compiled from the Ports Collection.

NetBSD

NetBSD's priority is portability and clean code. Its latest release shows the approach: NetBSD 11.0, announced on July 30, 2026, is described by the project as its first stable release with 64-bit RISC-V support. It also adds a very fast-booting virtual machine kernel and initial support for Qualcomm's Snapdragon X Elite.

OpenBSD

Theo de Raadt forked OpenBSD from NetBSD 1.0 in October 1995. The first release, 1.2, came in July 1996, and the project has shipped a release about every six months since. The original draft said OpenBSD "arrived in 1996"; the fork and the first release are different dates.

OpenBSD's focus is correctness and proactive security, and its default install is deliberately minimal. The project advertises only two remote holes in the default install in more than thirty years. That is the project's own claim. Its software is also widely used elsewhere: OpenSSH, LibreSSL and tmux all came out of OpenBSD.

DragonFly BSD, a fork of FreeBSD, is a smaller project with its own kernel design work.

Current versions

Project Current release Date Note
FreeBSD 15.1 June 16, 2026 14.4 (March 10, 2026) is also a production release.
OpenBSD 7.9 May 19, 2026 The project's 60th release.
NetBSD 11.0 July 30, 2026 The project says 11.1 is planned within about two months of 11.0.

Sources: FreeBSD, OpenBSD, NetBSD.

How BSD differs from Linux technically

One system versus many parts

This is the biggest practical difference. A BSD project develops the kernel and core userland together, in one repository, and releases them as one operating system. Linux is a kernel; distributions combine it with GNU tools and other software from separate projects. Neither approach is better in general. BSD's tends to feel more consistent, and Linux's gives more choice.

Kernels

FreeBSD, NetBSD and OpenBSD use monolithic kernels, as Linux does. Apple's XNU is different: its own source documentation calls it a hybrid kernel combining Carnegie Mellon's Mach with FreeBSD components and a C++ driver framework called I/O Kit. The BSD layer inside XNU has been modified heavily to work with Mach, so it should not be called plain FreeBSD.

Software installation

FreeBSD offers both binary packages and the Ports Collection, which builds software from source with your chosen options. Linux distributions mostly pick one model, such as apt, dnf or pacman. FreeBSD 15.1 also moves further toward a packaged base system: according to its release announcement, cloud images built that way now include pkg and can update the base system automatically on first boot.

File systems

FreeBSD has long supported ZFS, and its current releases use OpenZFS. ZFS also runs on Linux, but because of license incompatibility it cannot be built into the Linux kernel itself, so Linux users load it as a separate module. The Berkeley Fast File System, written by Kirk McKusick, was an early and influential design.

Security frameworks

The original draft claimed Linux has advanced mandatory access control that BSD lacks. That is not accurate. SELinux is Linux-specific, but FreeBSD has its own pluggable framework, the TrustedBSD MAC Framework. FreeBSD's documentation has historically described parts of it as experimental, so the honest summary is: different tools, with Linux's ecosystem around SELinux and AppArmor being much larger.

Licensing: the real divide

The BSD license is permissive. You can reuse the code in closed-source products if you keep the copyright notice. The GPL, which covers the Linux kernel, requires derivative works to be distributed under the GPL too.

That difference explains why BSD code appears inside commercial products. It is also easy to overstate. Apple does not ship macOS as a fully closed system built from BSD code: it publishes the Darwin sources, including XNU, while keeping much of the rest proprietary. The accurate point is that the BSD license allowed that mix, and the GPL would have imposed different obligations on the parts derived from GPL code.

Where BSD code actually runs

Here is what I could confirm and what I could not. Each row separates what the sources show from what is merely claimed.

Claim Status Note
Apple's operating systems build on Darwin and FreeBSD-derived code Confirmed Apple reported more than 2.5 billion active devices in January 2026. That is all Apple products, so it is the ceiling, not a count of BSD installs.
Netflix Open Connect servers run FreeBSD Confirmed The FreeBSD Foundation case study says the appliances run a lightly customized FreeBSD. The "32% of North American traffic" figure in the draft is old and I removed it.
PlayStation consoles run FreeBSD-based software Partly confirmed PS4 and PS5 are widely reported as FreeBSD-derived. Developers on the FreeBSD review site note the PS3 uses selected FreeBSD and NetBSD code rather than being a straight port.
Nintendo Switch uses FreeBSD Partly confirmed The console's license notices list FreeBSD components. It borrows parts; it is not a FreeBSD system.
Juniper, NetApp and Dell (Isilon) products use FreeBSD Confirmed Listed in the FreeBSD Handbook's "Who uses FreeBSD" section. I found no solid source for Panasonic and left it out.
WhatsApp ran on FreeBSD, then moved to Linux Not confirmed by the company The FreeBSD documentation team removed WhatsApp from its user list, citing its understanding that the use stopped after the Facebook acquisition. I found no statement from Meta.
Parts of Windows contain BSD code; NetBSD flew on NASA missions Unverified I could not find a reliable source in this review, so both claims are removed.

BSD versus Linux in practice

Hardware support

Linux usually supports new consumer hardware sooner, because vendors contribute drivers to it directly. BSD systems tend to be strongest on servers and network gear. NetBSD stretches the other way: its 11.0 release adds RISC-V, initial Snapdragon X Elite support and a Motorola 68000 virtual machine port. I could not verify the draft's claim that it supports more platforms than any other system, so I have not repeated it.

Performance

The draft made specific claims about socket and file-descriptor workloads without a source. I removed them. The best recent independent data point is a Phoronix test from December 2025 that ran FreeBSD 15.0 against Ubuntu 24.04.3 and 25.10 on an AMD EPYC 9965P server. Across more than 100 benchmarks, Phoronix found FreeBSD competitive and not far behind Ubuntu, with exceptions in both directions. SQLite was much slower on FreeBSD, and Ubuntu led in a localhost network test. Phoronix also noted that the other BSDs it tried could not boot on that machine.

Security: a 2026 reality check

BSD's reputation for security is earned in part, but 2026 produced two useful reminders.

  • FreeBSD: The FreeBSD project published advisory FreeBSD-SA-26:08 on March 26, 2026 for CVE-2026-4747, a remote code execution flaw in RPCSEC_GSS packet validation, reachable through the kernel NFS server when the kgssapi.ko module is loaded. The CVE record lists fixes in 15.0-p5, 14.4-p1, 14.3-p10 and 13.5-p11, and credits Nicholas Carlini using Claude.
  • OpenBSD: Anthropic's Frontier Red Team reported a 27-year-old flaw in OpenBSD's TCP SACK code that let a remote attacker crash a host. It is a denial-of-service bug, not code execution, and has been patched (errata patch 025 for 7.8).

Who says what: Anthropic, which makes the Claude models, published the report and says an AI model found both bugs. The FreeBSD advisory and CVE record independently confirm the FreeBSD flaw and its fix. The details of how the model found it are Anthropic's own account. The OpenBSD project still advertises its "two remote holes" line on its site as of release 7.9, and I did not find a project statement on whether the SACK bug changes that count.

The takeaway is not that BSD is insecure. Careful design reduces risk; it does not remove it, and old code in rarely used paths can hide serious bugs on any system.

Update (October 14, 2026)

  • FreeBSD 15.1 was released June 16, 2026. The announcement highlights wireless drivers updated from Linux 7.0 sources, packaged-base cloud images, a boot-time scheduler selection tunable and further C23 support.
  • OpenBSD 7.9 arrived May 19, 2026. Among its changes, the amd64 port now supports up to 255 CPUs, and it can run under Apple's virtualization framework.
  • NetBSD 11.0 arrived July 30, 2026 after a long release-candidate period. The project said it was shipping with open issues rather than delaying further, and listed them openly.

What users say

These are small samples from public forums. They are not representative surveys, but they show the recurring arguments.

  • In a FreeBSD Forums thread on the Phoronix benchmarks, one member concluded that untuned FreeBSD is slower than Ubuntu in some tests and faster in others. Another pointed out that the test compared ZFS on FreeBSD with ext4 on Ubuntu, which makes some results hard to compare.
  • On the Elixir Forum, several members said WhatsApp has moved to Linux. One linked a Hacker News comment from someone who said they were a former WhatsApp engineer. I could not verify that identity.
  • A BSD advocate on Mastodon pushed back on a mainstream article describing FreeBSD as harder than Linux, arguing that this is subjective and that the documentation is excellent. In a reply thread, another user countered that Linux has improved ease of use faster than the BSDs, and that FreeBSD's default install does not give you a desktop.

My take

I have not run any BSD for this article. This is my opinion from reading the sources and following the projects.

  • BSD's strongest case is coherence. When the kernel and tools are developed together, upgrades and documentation are easier to reason about, and the Netflix and appliance examples suggest the model works at scale.
  • I would not choose it for a new desktop or laptop. Linux's hardware and software support is wider, and even supporters of BSD admit the setup takes more work.
  • The security reputation deserves some skepticism. OpenBSD's record is impressive, but the 2026 bugs show that "audited for decades" is not the same as "bug-free". I would judge any system by how fast it patches, not by its slogan.

What this means for you

  1. If you run FreeBSD: check your patch level against the CVE-2026-4747 fixes (15.0-p5, 14.4-p1, 14.3-p10, 13.5-p11 or later) and update with freebsd-update. If you cannot patch immediately, avoid exposing NFS to untrusted networks and check whether kgssapi.ko is loaded.
  2. If you run OpenBSD: apply the 7.8 errata patch for the SACK bug, or run 7.9, which is newer than the patch.
  3. If you are curious: try a BSD in a virtual machine first. FreeBSD is the easiest starting point for servers; OpenBSD suits firewalls and learning; NetBSD suits unusual hardware.
  4. If you build commercial products: read the BSD license and your obligations. Permissive does not mean no conditions, since you still need to keep the notices.
  5. If you want a desktop: expect to spend time on drivers and configuration, and read the project handbook before you start.

Frequently asked questions

Is macOS a BSD?

Not exactly. macOS is built on Darwin, whose XNU kernel combines Mach with a BSD layer derived from FreeBSD. On top of that sits a large amount of Apple-specific and proprietary software.

Is BSD more secure than Linux?

There is no single answer. OpenBSD is designed around security and has a strong record, and FreeBSD has its own hardening tools. Linux has a much larger security tooling ecosystem and far more reviewers. As the 2026 bugs show, both need patching.

Which BSD should a beginner try first?

FreeBSD has the largest community and the most complete documentation, so it is the usual recommendation. Pick OpenBSD if your main goal is a small, security-focused system such as a router.

Sources

Tags

Post a Comment

0Comments

Post a Comment (0)