BSD, NeXT, Darwin, and macOS

The BSD descendants and Apple’s platforms share real Unix history, but they are not interchangeable products. Modern BSD projects grew from Berkeley’s work after legal and institutional transitions; NeXTSTEP combined Mach and BSD technology for a commercial workstation; Apple later built Darwin and its consumer platforms from that inheritance. Following the layers explains why a Mac terminal feels familiar while a macOS application stack is not simply “BSD.”

BSD after the settlement

The Berkeley Software Distribution began as additions to AT&T Unix at the University of California, Berkeley. Over time Berkeley-developed code—including influential TCP/IP networking work—became a large part of the system. The legal status of code derived from AT&T Unix complicated redistribution. After the federal court declined to grant USL's requested preliminary injunction in 1993, the parties signed a settlement in 1994; the resulting 4.4BSD-Lite release removed or replaced material identified through that process. It is misleading to say that all BSD code was suddenly “proven unrelated” to Unix. The practical result was a freely redistributable base from which current BSD systems could proceed.

Project	Origin and emphasis	Current character
FreeBSD	Started in 1993 from 386BSD-related work; emphasizes a cohesive general-purpose system and performance.	Used for servers, storage, networking, appliances, and desktops; its ports/packages ecosystem is a major part of the project.
NetBSD	Started in 1993 with portability as a central goal.	Runs on an unusually broad range of architectures and remains important for research, embedded work, and portable systems engineering.
OpenBSD	Forked from NetBSD in 1995 with security review, correctness, and integrated cryptography central to its culture.	Used for security-conscious servers, firewalls, and networking; projects such as OpenSSH originated there.

These projects are complete operating systems: each maintains a kernel, base userland, release process, documentation, and security policy. They use permissive BSD-style licenses in much of their base code, though a system contains code under several licenses. A permissive license allows reuse in proprietary products with conditions such as retaining notices; it creates a different exchange from the GPL, not an absence of obligations or community norms.

NeXTSTEP: Mach with BSD foundations

After leaving Apple in 1985, Steve Jobs founded NeXT. NeXTSTEP, introduced for NeXT workstations in 1989, used the Mach kernel architecture from Carnegie Mellon University together with substantial BSD components and a Unix user environment. Above that base, NeXT supplied its own object-oriented frameworks, graphical interface, development tools, and commercial integration. Mach was designed around ideas such as tasks, threads, virtual memory, and message passing; production systems that used Mach commonly made pragmatic choices rather than adopting a pure microkernel design.

NeXTSTEP’s development environment became historically important to web and application development, but its operating-system lineage should be stated precisely: it was Unix-derived and Unix-like, composed from Mach and BSD technology, with NeXT’s proprietary layers. It was not a continuation of a single Berkeley release, nor was every technology on a NeXT computer a BSD component.

Apple, Darwin, and XNU

Apple acquired NeXT in 1997. The resulting operating-system transition led to Mac OS X, first released in 2001 and later renamed OS X and macOS. Apple published Darwin, the open-source core that includes the XNU kernel and other foundational components. XNU’s name means “X is Not Unix”; it combines Mach-derived facilities with BSD code in a hybrid-kernel design. In broad terms, the stack includes Mach concepts, a BSD process and networking layer, an I/O subsystem, and architecture-specific code.

Layer	Examples	Availability and relationship
Darwin core	XNU, BSD-derived userland pieces, launch and networking foundations	Important source is published by Apple; it is a foundation, not a complete current macOS experience.
Apple platform layers	Quartz, Cocoa/AppKit or UIKit, many frameworks, applications, device integration	Much is proprietary and shipped under Apple’s platform terms.
Developer and command environment	`zsh`, BSD-style utilities, POSIX APIs, optional Apple developer tools	Familiar to Unix users, but versions and options can differ from GNU/Linux or a BSD release.

Apple later adapted this foundation for other devices. iOS, iPadOS, tvOS, watchOS, and visionOS use kernels and low-level technology in the Darwin/XNU family, but their frameworks, security model, distribution rules, and user interfaces differ by platform. In particular, an iPhone is not a general-purpose macOS installation with its desktop tools exposed. Shared ancestry does not imply interchangeable software or administration.

Open code is not the whole product

Darwin source availability has enabled inspection and derivative experimentation, but Apple controls the integrated macOS and mobile operating systems, their hardware support, signing infrastructure, and many frameworks. Conversely, FreeBSD, NetBSD, and OpenBSD make their complete base systems available as project releases, but can run third-party proprietary applications or firmware where hardware requires it. “Open” needs a subject: kernel source, base operating system, application framework, device boot chain, and app-distribution policy are separate questions.

UNIX certification and names

UNIX is a trademark administered by The Open Group, not a generic technical synonym for every Unix-like system. The Open Group certifies products that conform to the Single UNIX Specification. Apple has registered certain macOS releases as UNIX 03 conformant. A BSD project can be Unix-like and closely descended from Berkeley Unix without being sold under the UNIX trademark. Certification is a conformance and trademark program; it does not measure openness, age, security, or whether a command has every extension found on another system.

# macOS utilities often follow BSD conventions.
$ sed -i '' 's/old/new/' file.txt

# A GNU sed invocation commonly seen on Linux differs:
$ sed -i 's/old/new/' file.txt

# For a portable script, prefer a temporary file or test the target tools;
# do not label one set of options simply “Unix.”

Where these systems are used now

FreeBSD remains visible in storage and network appliances, hosting, content-delivery infrastructure, and systems that value its integrated base and licensing model. OpenBSD continues to influence secure networking and cryptographic tooling, while NetBSD’s portability serves hardware bring-up and long-lived architectures. Their market share is smaller than Linux’s in commodity cloud servers, but their code and engineering practices have a wider influence than a desktop-share comparison suggests.

macOS is Apple’s desktop and laptop platform, and Darwin/XNU technology underlies its current device operating systems. For developers, macOS offers a Unix-certified command and API environment alongside Apple-specific frameworks and tightly integrated hardware. The practical lesson is to name both the layer and the target: POSIX code may compile across systems; a BSD command option may not match GNU; a Cocoa application belongs to Apple’s platform rather than to BSD in general.