GNU (GNU's Not Unix) — The Free Software Operating System Project
GNU is a long-running project to create a free operating system and associated tools; it established the free software philosophy and the GNU General Public License and influenced many Linux-based systems.
Overview
GNU, an acronym for "GNU's Not Unix," is a broad collection of free software intended to form a complete computer operating system. The GNU Project promotes a model in which users can run, study, modify and redistribute software without proprietary restrictions, a principle commonly called free software. Many of the utilities and interfaces developed by GNU reproduce the functionality of traditional UNIX programs while emphasizing user freedom and collaborative development.
Image gallery
4 Images
Origins and philosophy
The GNU Project was announced by Richard Stallman in 1983. Stallman and early collaborators sought not only to recreate the technical capabilities of existing proprietary systems but to change the social and legal framework around software. To protect and perpetuate user freedoms, the project produced licensing mechanisms such as the GNU General Public License, which applies copyleft to ensure that modified and redistributed versions remain free in the same sense. The project's statements and writings continue to articulate ethical arguments about software freedom alongside practical development work.
Key components and tools
GNU is an ecosystem of programs rather than a single monolithic product. Its components include compilers, libraries, shells, editors and many userland utilities common to Unix-like systems. Notable pieces produced under the GNU umbrella include the GNU Compiler Collection (GCC), the GNU C Library (glibc), core utilities (coreutils), the Bourne Again SHell (bash), and development tools used to build and package software. Together these elements form the user-space layer that, when combined with a kernel, provides a functioning operating system.
Kernel work: GNU Hurd and alternatives
The GNU Project began development of a microkernel-based kernel family known as the GNU Hurd. The Hurd's architecture differs from many traditional kernels, but its development pace and adoption have been limited compared with other kernels. As a result, many systems that use GNU userland components pair them with alternative kernels; most commonly this has been the monolithic Linux kernel. The relationship between GNU userland and different kernels is a practical arrangement that lets GNU tools run on a wide range of hardware and distributions.
GNU and Linux: naming and collaboration
When the Linux kernel emerged, developers combined it with GNU userland tools to form complete systems. Some users and contributors refer to these systems as GNU/Linux to acknowledge the contribution of GNU components, while others use the shorter name Linux. This naming discussion reflects broader debates about credit, influence and the philosophical goals of the communities involved. Regardless of terminology, many distributions and projects integrate GNU software alongside other free and nonfree components.
Licensing, distribution and influence
The legal instruments and community norms developed by the GNU Project have had long-lasting effects on how software is shared and licensed. The GNU General Public License and related licenses have been widely adopted and have shaped the expectations of collaborative projects and organizations. GNU's emphasis on user freedom influenced both activist movements and technical practices in open development. Many developers and projects rely on GNU tools for building software, cross-compiling, testing and system maintenance.
Practical use and adoption
GNU components are ubiquitous in modern computing: they appear in developer toolchains, server environments, desktop distributions and embedded systems. Distributions that pair GNU userland with other kernels or modules provide a complete environment suitable for everyday use, scientific computing and production servers. Documentation and user guides explain how GNU pieces interoperate and how to customize systems for particular needs, and community resources help newcomers understand installation and contribution workflows.
Development and contribution
The GNU Project is sustained by contributors around the world. People interested in participating can consult project documentation and community channels to learn coding standards, translation practices, packaging procedures and governance. The project has long emphasized transparent collaboration and provides resources for contributors, while dialogues with other free software communities continue to shape priorities and technical directions.
Legacy and further reading
Historically, the GNU Project played a central role in defining the ideals of software freedom and in producing foundational tools still widely used today. For historical context and original statements from the project, see early announcements and archival materials from the time the project began in 1983. For technical details about the kernel work, consult materials on the GNU Hurd and on how GNU components are combined with alternative kernels such as the Linux kernel. The project's main documentation and developer guides provide practical instructions and background, including general information about building an operating system from GNU components and how to join the developer community of contributors.
Readers seeking an introduction to free software principles can follow links and resources that discuss the core ideas of free software, the relationship to proprietary systems like UNIX, and the technical distinctions involved in kernel and userland design (kernel architectures). These materials help explain why GNU remains an influential project in computing and how its work continues to underpin many systems used today.
History
After the announcement in 1983 and the subsequent creation of the GNU Project in 1984, which aimed to develop GNU, the GNU operating system has been actively developed ever since. GNU was designed to be as compatible as possible with Unix. There were several reasons for this decision: First, it was certain that most companies would reject a fundamentally new operating system if the programs they used would not run on it. On the other hand, the architecture of Unix allowed for fast, easy, and distributed development, since Unix consists of many small programs, most of which can be developed independently.
In 1990, a development system with the GNU C compiler and many system programs was ready, but a kernel was still missing. The Free Software Foundation then decided (after much back and forth) to use the Mach kernel. Based on this, a multiserver operating system was to be written so that the system could be extended more easily by further components and users without administrator rights could also integrate their own components without endangering the stability of the overall system.
The multiserver system was christened GNU Hurd. However, since it made heavy use of multithreading, debugging proved to be very difficult. The project became very large and difficult to manage. At the same time, developers were drawn to the much more pragmatically developed Linux, thus missing GNU Mach and GNU Hurd. The development of these parts was slow. During this time, a running gag developed where users would ask when Hurd would be ready, and the answer would refer to the respective next year. Hurd is therefore often referred to as vaporware.
In 1998, Marcus Brinkmann started the Debian GNU/Hurd project to give development more momentum again. The infrastructure of the Debian project was made usable for GNU Mach and GNU Hurd, allowing a larger number of applications to be ported to the system for the first time. A usable installation routine was created as part of Debian GNU/Hurd, also X11, Gnome and KDE were ported to the platform. In addition, it benefited from the mature package management using apt-get, dpkg, and the other tools Debian provides for system management. Brinkmann also extended GNU Hurd with a Unicode-enabled console that is based on a client/server architecture and thus clearly surpasses the Linux console in flexibility.
In 2001 there were also efforts to port GNU Hurd from the Mach microkernel GNU Mach to an L4 kernel, a second generation microkernel. This L4 Hurd project, like Debian GNU/Hurd, was also significantly driven and coordinated by Marcus Brinkmann. In February 2005 the first phase of this port was finished. First small programs can be executed under a GNU-Hurd-L4 system since then. However, neither a shell nor the GNU software is available yet, so interaction with the system is limited to using the kernel debugger for the time being. In January 2006 there were considerations to use Coyotos instead of the L4 microkernel.
Kernel
→ Main article: GNU Hurd
The GNU Project envisions the GNU Hurd kernel for GNU. The decision for this experimental kernel was an important reason for the stagnant development of a usable GNU operating system.
GNU Mach is the GNU Project's favored microkernel for hardware abstraction. It is an implementation of the Mach kernel and currently (as of December 2015) the default microkernel of GNU Hurd. GNU Mach so far only runs on machines of the deprecated Intel 32-bit architecture. More ports are planned for the future, though development is stagnating. Since the combination of Mach and Hurd is thus still difficult to use productively, Linux is very often used as the kernel and the entire system is just called "Linux" instead of GNU/Linux.
"Hurd/L4" or "L4-Hurd" is a project that was supposed to port "GNU Hurd" to the L4 microkernel and thus replace GNU Mach in the long run. However, L4 has turned out to be unsuitable.
Related articles
Author
AlegsaOnline.com GNU (GNU's Not Unix) — The Free Software Operating System Project Leandro Alegsa
URL: https://en.alegsaonline.com/art/39338