FreeBSD 2.0 Ships, Finally Free of AT&T Code
Released November 22, 1994 and rebased on 4.4BSD-Lite, FreeBSD 2.0 was the first release legally clear of the USL v. BSDi lawsuit's shadow — the release that secured the project's legal future.
Real, dated releases and announcements — verified against official sources, not speculation.
Released November 22, 1994 and rebased on 4.4BSD-Lite, FreeBSD 2.0 was the first release legally clear of the USL v. BSDi lawsuit's shadow — the release that secured the project's legal future.
How a disagreement over FreeBSD 5's threading and SMP architecture led Matt Dillon to fork FreeBSD 4.8 into an entirely separate project in 2003.
Created by developer Justin Gibbs on March 15, 2000 as a 501(c)(3) non-profit, the Foundation gave FreeBSD a legal entity for funding development, licensing Java binaries, and sponsoring the project's growth.
How the FreeBSD Foundation's sponsored-development model paid for real, shipped improvements to OpenSSH compatibility and the iwlwifi driver stack rather than just donating money in the abstract.
FreeBSD 15.0's actual shipped feature set: 64-bit UFS inodes by default, MIT Kerberos replacing Heimdal, a native inotify(2) implementation, and the first release supporting binary updates via pkg.
The base system's source repository moved to Git in December 2020, following the documentation repo by weeks and preceding the ports tree by several months.
ZFS arrived in FreeBSD's base system in the late 2000s, but installing directly onto a ZFS root without manual command-line setup took years longer to become a guided installer option.
Founded in July 2003 by Michael Phipps in Rochester, New York, Haiku, Inc. gave the OpenBeOS/Haiku project a formal nonprofit structure for accepting donations and funding contractor work.
After a design drafted in January 2011 and development under funded contracts, Haiku's packagefs-based package management shipped in September 2013 — reshaping how software gets installed on the system.
The first beta release of Haiku R1 arrived on September 28, 2018 — a milestone that had been anticipated for years, marking the project's transition from alpha-quality software toward an eventual stable 1.0.