Introduction to GNU/Linux, the Linux kernel, distributions, package management, and desktop environments.
GNU/Linux is a common name for Unix-like operating systems that combine the Linux kernel with substantial parts of the GNU Project and software from many other projects.
In everyday use, people often call the complete operating system simply “Linux.” That usage is widespread, but technically Linux is the kernel: the privileged component that manages CPUs, memory, devices, processes, networking, filesystems, and other low-level resources.
A distribution such as Debian, Ubuntu, Fedora, Arch Linux, or openSUSE builds a complete system around that kernel by adding libraries, user-space tools, an init system, package management, services, security policies, an installer, and optionally a graphical desktop.
For a broader introduction to what an operating system does, see our guide to operating systems and their core components.
The GNU Project was announced by Richard Stallman in September 1983 and development began in 1984 with the goal of creating a free Unix-compatible operating system.
GNU produced or helped establish major components such as GCC, the GNU C Library, Coreutils, Bash, Make, GDB, Emacs, and many other tools. The Free Software Foundation was founded in 1985 to support free-software development and advocacy.
Linux is the kernel Linus Torvalds began developing in 1991. It sits between hardware and user-space software, handling process scheduling, memory management, device drivers, networking, filesystems, security mechanisms, and system calls.
Linux was released as free software under the GNU GPLv2 in 1992, which made it possible to combine it with the already existing GNU environment and other free software.
When a distribution uses Linux as its kernel and a substantial portion of its user space comes from GNU, GNU/Linux is a technically descriptive name for that combination.
Not every Linux-based system is GNU/Linux. Android uses the Linux kernel but a very different user-space platform. Alpine Linux uses musl and BusyBox instead of many traditional GNU components. Embedded systems can use even smaller combinations.
In this article, “GNU/Linux” refers specifically to the traditional combination, while “Linux” refers to the kernel or to the broader Linux ecosystem where appropriate.
GNU predates Linux. According to the GNU Project’s own history, by the beginning of the 1990s most major components required for a free Unix-like operating system already existed, but a production-ready kernel was still missing.
In 1991 Linus Torvalds began developing Linux while studying at the University of Helsinki. He was influenced by Unix and by his experience with MINIX, Andrew S. Tanenbaum’s educational operating system, but Linux was not a modified copy of MINIX. It was independently developed.
Linux moved to the GPLv2 in 1992. Developers could then combine it with GCC, Bash, libc, Coreutils, and many other existing components.
Another common simplification needs correction: the GNU Project did not adopt Linux as the official GNU kernel. GNU continued developing the Hurd. Independent communities and distribution projects combined GNU and Linux into installable systems.
Debian, announced in 1993, explicitly used the name Debian GNU/Linux. Slackware also appeared in 1993 and remains one of the oldest active distributions.
The kernel executes with the highest level of privilege in the system. Its responsibilities include:
Normal applications usually do not manipulate hardware directly. They call libraries and operating-system APIs, which ultimately request services from the kernel through system calls.
For more detail, see our hardware drivers guide.
As of October 5, 2026, kernel.org lists Linux 7.2.9 as the current stable kernel. The 7.3 series is still in release-candidate development.
A distribution does not need to ship the newest upstream kernel to be secure or current. Debian, Ubuntu, RHEL, and other long-lived platforms commonly maintain selected kernel branches for years while backporting security fixes and hardware support.
kernel.org also maintains several longterm branches. At the time of this update they include 6.18, 6.12, 6.6, 6.1, 5.15, and 5.10.
A modern distribution normally integrates several layers:
| Layer | Examples |
|---|---|
| Firmware / boot | UEFI, shim, GRUB, systemd-boot |
| Kernel | Linux and loadable modules/drivers |
| C library | glibc, musl |
| Core utilities | GNU Coreutils, BusyBox, util-linux |
| Init and services | systemd, OpenRC, runit, s6 |
| Package management | APT/dpkg, DNF/RPM, pacman, Zypper, APK, Portage |
| Networking | NetworkManager, systemd-networkd, iproute2, nftables |
| User interface | Bash/Zsh, GNOME, KDE Plasma, Xfce, Cinnamon, LXQt |
| Applications | servers, browsers, editors, compilers, and user tools |
A distribution is therefore much more than “Linux with a different logo.” The project decides which versions to package, how long to maintain them, what patches to apply, which architectures to support, and what user experience to provide.
On many current distributions, systemd runs as PID 1 and manages system services. It handles dependencies, socket activation, service supervision, cgroup integration, and tools such as systemctl and journalctl.
systemd is not mandatory for using Linux. Alpine commonly uses OpenRC, and some distributions use runit, s6, or other alternatives.
This is an important feature of the ecosystem: sharing the Linux kernel does not require every distribution to share the same user-space architecture.
GNU/Linux can be used entirely through graphical interfaces, but the command line still plays an unusually important role.
Servers are commonly administered over SSH and automated with Bash, Python, Ansible, or similar tools. On desktops, the terminal complements graphical applications when operations need to be repeatable or when low-level diagnostics are required.
It is also useful to distinguish a terminal from a shell. The terminal is the application or interface where you type. Bash, Zsh, Fish, and other shells interpret commands.
GNU/Linux has no single desktop. GNOME, KDE Plasma, Xfce, Cinnamon, MATE, LXQt, and many others are available.
By 2026, Wayland is the default graphical session in many mainstream distributions, while X11/X.Org remains available in various environments for compatibility.
The following images come from the original Universo Digital article. Several are historical, especially those showing KDE 4, and we are preserving them because they help illustrate how Linux desktop environments evolved.
One of the most visible differences between distributions is package management.
| Distribution family | Common format / tools |
|---|---|
| Debian / Ubuntu | .deb, dpkg, APT |
| Fedora / RHEL / Rocky / AlmaLinux | .rpm, DNF |
| openSUSE / SUSE | .rpm, Zypper |
| Arch Linux | Arch packages, pacman |
| Alpine Linux | .apk, apk-tools |
| Gentoo | Portage / emerge |
Package managers query repositories, resolve dependencies, install files, and update the system in a consistent way. This is different from downloading arbitrary installers from unrelated third-party websites.
There are also cross-distribution desktop application formats such as Flatpak, Snap, and AppImage. They usually complement rather than replace the distribution’s native package manager.
GNU/Linux security is not provided by one magical feature. Traditional Unix permissions are combined with several modern mechanisms:
sudo and privilege separation;Linux is not “immune to viruses.” Poorly configured servers, vulnerable services, weak credentials, or untrusted packages can compromise a Linux system just as they can compromise other platforms.
Linux supports many filesystems. Common native choices include ext4, XFS, and Btrfs, while support also exists for FAT/exFAT, NTFS, and many others.
ZFS is widely used on Linux as well, although licensing differences mean it is normally distributed outside the upstream Linux kernel tree.
The best filesystem depends on the workload. Workstations, database servers, NAS systems, snapshot-heavy workloads, and embedded systems do not necessarily have the same requirements.
Linux containers use kernel features such as namespaces and cgroups to isolate processes while sharing the host kernel. Docker, Podman, Kubernetes, and LXC build different operating models on top of those primitives.
A virtual machine runs its own kernel inside virtualized hardware. That is why KVM can run a Windows guest, while an ordinary Linux container does not contain an independent Windows kernel.
See our introduction to virtualization for a deeper comparison.
GNU/Linux is especially strong in servers because of its automation model, remote administration, networking tools, long-lived distributions, and ability to build small systems with only the required services.
It is also foundational to much of cloud infrastructure, containers, web hosting, and high-performance computing.
That does not make Linux “server-only.” Modern desktop distributions support browsers, office suites, multimedia creation, development tools, gaming, and a growing selection of commercial software.
There is no single “best Linux distribution.” Choose based on support lifecycle, hardware, software requirements, and how much system maintenance you want to perform yourself.
| Distribution | Typical focus | Official site / download |
|---|---|---|
| Debian 13 “Trixie” | Stability, servers, and a major base for derivatives | Debian · Downloads |
| Ubuntu 26.04 LTS | Desktop, servers, cloud, long-term support | Ubuntu · Downloads |
| Fedora Linux | Recent upstream technologies and Red Hat ecosystem development | Fedora · Downloads |
| Arch Linux | Rolling release, user control, current packages | Arch Linux · Downloads |
| openSUSE | Leap for a stable model and Tumbleweed for rolling release | openSUSE · Downloads |
| Linux Mint | Desktop ease of use | Linux Mint · Downloads |
| Alpine Linux | Minimal systems, containers, small attack surface | Alpine · Downloads |
Debian’s current stable branch is 13.7 Trixie. Ubuntu’s current long-term support release is 26.04 LTS, with the 26.04.1 point release already available.
Arch Linux and openSUSE Tumbleweed continuously deliver newer packages. Debian Stable, Ubuntu LTS, RHEL, and similar enterprise-oriented distributions favor longer support windows and more controlled change.
“Rolling release” does not automatically mean unstable, and “LTS” does not mean the software never changes. They are different release and maintenance models.
Because the ecosystem allows projects to combine components and policies in many different ways. Distributions can differ in:
This can be confusing to newcomers, but it also prevents the entire ecosystem from depending on one vendor or one technical decision.
For a general desktop, Ubuntu LTS, Linux Mint, Fedora Workstation, or one of Ubuntu’s official flavors are reasonable starting points. For server administration, Debian and Ubuntu Server have extensive documentation. For users who want to understand the system by assembling more of it manually, Arch Linux or Gentoo provide a different learning experience.
The most important criteria are hardware support, required applications, maintenance lifecycle, and documentation.
Most distributions publish ISO images that can be written to a USB drive. Our bootable USB tools guide compares Rufus, Ventoy, balenaEtcher, Fedora Media Writer, and other approaches.
We also maintain version-specific tutorials, including:
Historical installation guides document those releases accurately, but a new production installation should use a distribution version that still receives security updates.
GNU/Linux is not one closed product. It is a family assembled from a kernel, system libraries, user-space tools, services, package managers, and thousands of independent projects that distributions integrate in different ways.
Understanding those layers—kernel, user space, distribution, package system, services, and desktop—removes much of the confusion that new users encounter and explains why two “Linux” systems can look very different while sharing the same technological foundation.
Learn PHP 8.5 from scratch: syntax, databases, Composer, PSR, Laravel, Symfony, modern runtimes, APIs, security,…
Step-by-step guide to installing VirtualBox Guest Additions 7.2.20 on Linux: kernel headers, modules, Secure Boot,…
An introduction to Kali Linux 2026.2: authorized security testing, rolling updates, APT changes, virtual machines,…
A practical guide to software test automation: unit, integration, API, contracts, Selenium, Playwright, Cypress, Appium,…
A complete networking roadmap for future sysadmins: Ethernet, IPv4/IPv6, subnetting, VLANs, routing, DNS, DHCP, Linux,…
History and architecture of Evelyn Berezin’s United Airlines reservation system, distinguishing it from the earlier…