Dev ToolsArticle Dialog’s removal finishes a long cleanup that mostly matters to teams embedding or redistributing FreeBSD.
Lenn Voss
FreeBSD has spent more than a decade chipping GPL-licensed code out of its base system. As of the FreeBSD 16 development tree, that work is done. The last holdout, the GNU dialog
utility and its library, has been retired along with the remaining consumers that still depended on it. With that merge, the GNU subtree in base is gone.
This is not a kernel rewrite or a new architecture story. It is a licensing milestone. For teams that ship FreeBSD as firmware, network appliances, or embedded platforms, a base tree free of GPL is a real compliance simplification. For everyone else, it is mostly the formal end of a cleanup that was already 95% finished.
The Last Mile Was Dialog #
The sequence is straightforward. The FreeBSD installer moved to bsddialog years ago as a BSD-licensed replacement for the old text UI. The remaining in-tree consumer was dpv
(and related pieces like libdpv
and libfigpar
). Those had already been disconnected for more than two years and were absent from FreeBSD 14 and 15. Once nothing in base still called dialog, the project could delete it.
A review that landed in the FreeBSD 16 tree retired dialog itself, those leftover dpv
pieces, and then the empty GNU subtree. Earlier in the 16-current cycle, GNU diff3
had already been swapped for a BSD-licensed version, leaving dialog as the final GPL component. FreeBSD 16.0 is still targeted for December 2027, so the change is in the development branch now and will ship with that release.
None of this is surprising if you have watched FreeBSD’s toolchain history. The bigger earlier step was the move from GCC to the BSD-licensed Clang/LLVM stack as the default compiler. That removed a large, hard-to-replace GPL dependency from the build system. Dialog was small by comparison: a userland text UI layered on ncurses. Replacing it was more about effort and priority than deep computer science.
Base System Purity Is Not the Whole OS #
“GPL-free base” has a precise meaning. It covers the core operating system tree: kernel, essential userland, installer, and the utilities that ship as part of the base system. It does not cover the ports tree or packages. Install a typical desktop or server stack from packages and you will still pull in plenty of GPL software. That has always been true, and nothing about FreeBSD 16 changes it.
There is also the usual pedantry about other copyleft-ish licenses. OpenZFS in FreeBSD is CDDL, which is file-based copyleft. That is not GPL, and FreeBSD has never treated it as disqualifying for base. OpenBSD’s stricter purity bar is a different project with different goals. FreeBSD’s stated aim was eliminating residual GPL from base, not achieving a pure public-domain-or-BSD-only tree.
For license auditors, the distinction still matters. Auditing the base system for redistribution is now simpler: you are looking at BSD (and a few other non-GPL) licenses, not a mixed bag that includes GNU dialog. Auditing the full installed image still means reviewing every port you add.
Who Actually Cares in Practice #
The practical winners are product teams that embed or redistribute FreeBSD.
If you build network gear, storage appliances, firewalls, or closed-source platforms on FreeBSD, the BSD license has always been the selling point. You can take the code, modify it, and ship binaries without releasing your changes, as long as you keep the required attribution. GPL components in base complicated that story. Even a small utility like dialog forced either careful isolation, a reimplementation, or acceptance of GPL obligations if that code was distributed as part of the product. With dialog gone, a stock FreeBSD 16 base image no longer carries that footgun. Compliance checklists get shorter. Legal review of “what ships in our firmware image” gets cleaner. That is the real product impact, not a philosophical victory lap.
Typical FreeBSD server or workstation users will notice almost nothing. The installer already used bsddialog. dpv
was already dark. Day-to-day package management, jails, ZFS, and networking are unchanged. If your workflow never touched dialog scripts or the old GNU subtree, FreeBSD 16 will feel like any other major release cycle.
For developers writing installer-style tools or text UIs on FreeBSD, the message is simple: use bsddialog (or ncurses directly), not the old dialog package from base. If you still need the classic dialog interface for scripts, it remains available via ports under its packaging name; it is just no longer part of the base system you get with a stock install.
Trade-offs That Did Not Magically Disappear #
Removing GPL from base does not make FreeBSD “more free” in the FSF sense. It makes FreeBSD more permissive for proprietary derivatives. That is a deliberate design choice, not a bug. Companies have long preferred FreeBSD (and other BSD-derived stacks) for exactly this reason: Juniper, NetApp, Citrix, and Apple’s Darwin lineage are the usual examples. The completed purge reinforces that position; it does not invent it.
There is a cost in engineering attention. Years of incremental replacements (compiler, diff tools, dialog, and the glue around them) diverted effort that could have gone elsewhere. The project judged the licensing clarity worth it. Whether that trade-off was correct depends on whether you ship FreeBSD-based products. If you do, the payoff is concrete. If you only run FreeBSD as a host OS, you mostly inherited the cleanup for free.
One more caveat: “base is clean” only helps if you actually ship base. Pull a fat package set, vendor a Linux userland in a jail, or bundle third-party GPL tools into your image and you are back to a mixed license surface. The milestone is real for the tree FreeBSD maintains. Your product image is still your responsibility.
Bottom Line #
FreeBSD 16 finishing the GPL purge is a genuine completion of a long-running goal, not hype. The last commit was small because the hard work (Clang, installer migration, disconnecting dead consumers) already happened. What changes for professional developers is mainly the compliance story for embedded and appliance work: a FreeBSD 16 base system no longer forces GPL analysis for residual GNU utilities.
Treat it as a licensing hygiene win that ships with the December 2027 release train. If you redistribute FreeBSD, plan your image and attribution review around a cleaner base. If you just run FreeBSD servers, note the milestone and move on. The interesting FreeBSD work for most of us remains elsewhere: laptop hardware support, drivers, and the usual ports churn. The GPL chapter in base is closed.
Sources & further reading #
[FreeBSD 16 Retires the Last of Its GPL Code from Its Base System](https://www.phoronix.com/news/FreeBSD-16-Goes-GPL-Free)— phoronix.com -
[FreeBSD 16 Retires the Last of Its GPL Code - Slashdot](https://bsd.slashdot.org/story/26/07/15/1727252/freebsd-16-retires-the-last-of-its-gpl-code)— bsd.slashdot.org -
[FreeBSD 16 Completes Removal of All Residual GPL Code from Its Base System](https://pbxscience.com/freebsd-16-completes-removal-of-all-residual-gpl-code-from-its-base-system/)— pbxscience.com -
[Only one piece of GPL software left in FreeBSD | The FreeBSD Forums](https://forums.freebsd.org/threads/only-one-piece-of-gpl-software-left-in-freebsd.101699/)— forums.freebsd.org -
[⚙ D55424 Retire dialog](https://reviews.freebsd.org/D55424)— reviews.freebsd.org
[Lenn Voss](https://sourcefeed.dev/u/lennart_voss)· Cloud & Infrastructure Writer
Lenn writes about cloud platforms, Kubernetes internals, and the infrastructure decisions that quietly make or break engineering organizations. Based in Berlin's vibrant tech scene, they have a talent for turning dense platform-engineering topics into prose that people actually finish reading.
Discussion 0 #
No comments yet
Be the first to weigh in.