LLMpediaThe first transparent, open encyclopedia generated by LLMs

BSD licenses

Generated by DeepSeek V3.2
Note: This article was automatically generated by a large language model (LLM) from purely parametric knowledge (no retrieval). It may contain inaccuracies or hallucinations. This encyclopedia is part of a research project currently under review.
Article Genealogy
Parent: Linux Hop 4
Expansion Funnel Raw 46 → Dedup 7 → NER 5 → Enqueued 5
1. Extracted46
2. After dedup7 (None)
3. After NER5 (None)
Rejected: 2 (not NE: 2)
4. Enqueued5 (None)
BSD licenses
NameBSD licenses
AuthorRegents of the University of California
VersionVarious
CopyrightBerkeley Software Distribution
Published1980s–present
GPL compatibleSome variants
LinkingPermissive

BSD licenses are a family of permissive free software licenses, imposing minimal restrictions on the use and distribution of covered software. Originating from the Berkeley Software Distribution, a reimplementation of the Unix operating system, these licenses are known for their simplicity and business-friendly terms. They allow for proprietary derivative works and are widely used in both open-source and commercial products, from foundational internet software to modern operating systems like FreeBSD and macOS.

Overview

The core principle is to grant extensive freedom, requiring primarily the preservation of copyright notices and disclaimers. This contrasts with copyleft licenses like the GNU General Public License, which mandate that derivative works remain under the same terms. The permissive nature has made them attractive for incorporation into proprietary products developed by companies such as Microsoft, Apple Inc., and Cisco Systems. Key software released under these terms includes the original TCP/IP stack, the X Window System, and the ZFS file system.

History and development

The original form was created during the 1970s and 1980s for the Berkeley Software Distribution, developed at the University of California, Berkeley by the Computer Systems Research Group. Early distributions of BSD contained code from the proprietary Unix system owned by AT&T Corporation, leading to the USL v. BSDi lawsuit. This legal dispute prompted a re-engineering effort to create a complete, unencumbered operating system, culminating in 4.4BSD-Lite. The need for clear, unencumbered licensing for this clean codebase solidified the modern forms, influencing subsequent projects like NetBSD and OpenBSD.

Variants and terms

Several distinct versions exist, each with specific clauses. The original, often called the "4-clause" license, included an advertising clause requiring acknowledgment in all promotional materials, which was later deemed problematic. The "3-clause" or "New" version, now the most common, removed this clause, retaining only requirements for maintaining copyright notices, providing the full text, and including a non-endorsement disclaimer. The "2-clause" or "Simplified" version further omits the non-endorsement clause, while the "0-clause" variant is effectively a dedication to the public domain. These evolutions were driven by communities like the FreeBSD Project and the Open Source Initiative.

Comparison with other licenses

When contrasted with the GNU General Public License or the Mozilla Public License, the permissive approach places fewer obligations on downstream users, allowing code to be integrated into closed-source products. This differs fundamentally from the strong copyleft of the GNU Affero General Public License. Compared to other permissive licenses like the MIT License or Apache License 2.0, the terms are often shorter and similarly business-friendly, though the Apache License 2.0 includes explicit patent grants. The Free Software Foundation and the Open Source Initiative approve most variants for their compliance with the Open Source Definition and the Free Software Definition.

Usage and adoption

Adoption is extensive across critical infrastructure and consumer technology. The FreeBSD, OpenBSD, and NetBSD operating systems are direct descendants. Core components of Apple Inc.'s macOS and iOS are derived from Darwin, which uses this licensing. Key networking software, including the BIND name server and the OpenSSH suite, also employ these terms. Their permissiveness makes them popular for embedded systems, cloud infrastructure, and projects within the Apache Software Foundation, alongside code from the Linux kernel.

Legal analysis generally considers the terms straightforward, with fewer ambiguities than complex copyleft licenses. Compatibility with the GNU General Public License is a noted area of nuance; code under the 2-clause and 3-clause versions can be combined with GPL-licensed code, but the original 4-clause version is incompatible due to the additional restrictions. Courts in the United States and the European Union have upheld the enforceability of similar permissive license terms in cases like Jacobsen v. Katzer. The clarity of the terms reduces legal overhead for organizations like Google and IBM, facilitating broad commercial use.