Video summary

FreeBSD Eliminated All Its GPL Code

Main summary

Key takeaways

News and Commentary

Overview

The video argues that FreeBSD has finally removed all remaining GPL-licensed code from its base system, presenting this as the culmination of a long-term, licensing-driven policy rooted in the BSD tradition—with an emphasis on permissive licensing rather than copyleft.

1) Licensing culture: GPL vs. BSD

  • The speaker contrasts Linux’s GPL heritage with BSD’s permissive licensing roots.
  • They note that Linux’s early licensing was described as chaotic, later stabilized by GPLv2. They also reference Torvalds’ criticism of GPLv3, arguing it added restrictions, and they highlight the “give source, take modifications, return them” model as more aligned with GPLv2.
  • The BSD lineage is traced back to Berkeley Unix and the four-clause BSD license (itself derived from earlier 3-clause/2-clause/0-clause variants).
  • Core claim: BSD licenses do not require derivative works to be open sourced, though they may encourage openness.

2) What changed in FreeBSD: removal of the last GPL component

  • The video highlights a recent FreeBSD change: retiring Dialog, described as the last remaining GPL software component in the FreeBSD base system.
  • The speaker states that the installer moved away from BSD Dialog earlier, and that other dependent components (e.g., DPV and related libraries) were retired previously.
  • With Dialog removed, the GNU-related “subtree” in the FreeBSD base system is described as effectively an empty shell.
  • Conclusion: after the commit, FreeBSD’s userland/base system is free of GPL code.

3) Why FreeBSD did this (and why it’s not “new”)

  • The video pushes back against “anger” or criticism, arguing that permissive licensing has been central to FreeBSD since the project began.
  • The speaker cites FreeBSD project goals and “why you should use FreeBSD” style material to support claims such as:
    • FreeBSD aims for software “without strings attached”, including suitability for commercial use.
    • BSD licensing enables use/modification and (optionally) non-disclosure of changes when distributing modified versions.
    • GPL is framed as creating complications for commercial adoption due to copyleft requirements.

4) Comparisons and practical ecosystem reality

  • The speaker acknowledges that companies can still adopt BSD-derived code without contributing back, citing examples like:
    • Apple using parts of BSD/OpenBSD-style code across macOS/iOS ecosystems (presented as reuse of components/tools rather than direct forks).
    • Sony (PlayStation) using FreeBSD-derived OS components for years.
  • The argument: this “no need to upstream everything” outcome aligns with BSD’s purpose—maximizing adoption rather than enforcing reciprocal contribution.

5) The “why keep GPL at all?” question answered

  • The video explains that FreeBSD previously included some GPL components, largely attributed to Linux’s popularity and momentum:
    • As Linux grew dominant with GPL-based tooling, BSD systems adopted some components for practicality.
    • It also mentions an AT&T/BSD patent-related controversy that delayed BSD momentum compared with Linux, after which GPL-based norms became harder to avoid.

6) What the removal means for users

  • The speaker emphasizes that the issue is about what must exist in FreeBSD’s base system to meet FreeBSD’s stated goals.
  • Users are still free to install GPL software separately if they want.
  • The debate is framed as primarily about base system compliance, not user choice.

Presenters or contributors

  • No other presenters or named contributors are referenced in the subtitles.
  • The speaker is the video narrator/creator (not explicitly identified by name).

Original video