The GNU Project
Free software principles, the GPL, and the missing kernel
In the early 1980s proprietary software was becoming the default model for commercial computing. Richard Stallman, then at MIT, argued that users should be able to run, study, share, and modify the programs they depended on. In 1983 he announced the GNU Project: a complete Unix-compatible system that would remain free under those terms.
Goals and naming
GNU is a recursive acronym for "GNU's Not Unix." The point was not nostalgia for Unix so much as a free replacement for the tools people already knew. Stallman's Free Software Movement treated licensing and ethics as part of the engineering problem, not an afterthought.
Building blocks
Practical work followed the philosophy:
- GNU General Public License (GPL) — First released in 1989, it required that redistributed versions remain free software under the same terms.
- Core tools — Projects such as GCC, GNU Emacs, and Bash became standard pieces of the free software toolchain.
- User control — Source availability and modification rights were design constraints, not marketing claims.
By the early 1990s GNU had most of a free system except a production-ready kernel.
GNU and Linux
In 1991 Linus Torvalds released the Linux kernel under a free license. Combined with GNU userland tools, the result was the system many people call Linux and Stallman prefers to call GNU/Linux. The partnership was technical: GNU needed a kernel; Linux needed a complete environment. Stallman continued to emphasize that the license and freedom goals mattered as much as the kernel's success.
Influence
The GPL became one of the most used free software licenses. The idea that shared source and copyleft could support serious infrastructure influenced projects far beyond GNU itself — including large parts of the modern open source stack. The project also left a durable argument: that control over software is a user right, not only a vendor feature.