Is Linux an operating system or a kernel?
Linux is technically the kernel. In ordinary speech, people often say Linux to mean a complete operating system built around that kernel, such as Ubuntu, Debian, or Fedora.
Linux from first principles
A calm, complete guide to how Linux works.
Linux Atlas is a structured knowledge base for understanding Linux from the ground up: distributions, commands, filesystems, permissions, processes, packages, networking, boot, logs, storage, and security.
Linux ecosystem overview
A distribution turns the Linux kernel and user-space software into a usable operating system.
Appswhat you use
Shells and servicesuser space
Packagesdistro layer
Kernelresource control
Hardwaredevices
Definition
Linux is a kernel, a family of systems, and a way of organizing computing knowledge.
The kernel manages hardware and core resources. A distribution adds the installer, package repositories, system services, shells, desktop components, documentation, and defaults that make a complete system.
What Linux is
Begin with the difference between the Linux kernel, GNU tools, desktop environments, and distributions.
Choose a distribution
Learn why distros exist and how beginners, developers, server admins, and older PCs need different defaults.
Learn the shell
Understand command structure, quoting, pipes, redirection, PATH, aliases, and shell startup files.
Customize safely
Learn what desktop environments, window managers, dotfiles, bars, launchers, and Hyprland actually control.
Use the command library
Look up common commands with explanations written for humans instead of terse manual-page language.
Explore the library
Major Linux topics, organized for reading and reference.
Start with the concepts, then drop into command pages and distro comparisons when you need practical details.
Linux basics
Understand kernels, distributions, GNU/Linux, open source, and the architecture of a Linux system.
Distributions
Compare Ubuntu, Debian, Fedora, Arch, Mint, Alpine, Rocky, Kali, and more.
Commands
A practical command reference with syntax, examples, safety notes, and related tools.
Filesystems
Learn the root directory, mount points, virtual filesystems, and where Linux stores things.
Permissions
Make sense of users, groups, read/write/execute bits, chmod, chown, umask, and special bits.
Processes
See how Linux starts programs, tracks process IDs, handles signals, and manages services.
Package managers
Compare apt, dnf, pacman, zypper, apk, dpkg, and rpm as dependency managers.
Networking
Decode IP addresses, DNS, localhost, ports, TCP, UDP, sockets, and first-step troubleshooting.
Boot process
Follow firmware, UEFI, bootloader, kernel, initramfs, systemd, and login in order.
Customization
Understand desktop environments, window managers, Wayland compositors, dotfiles, themes, and Hyprland safely.
Troubleshooting
Use logs, journalctl, error messages, service state, packages, disks, and network checks calmly.
Most searched
Fast answers to common Linux questions.
These topics are frequent stumbling blocks because they connect several Linux concepts at once.
What does sudo do?
How privilege elevation works and why it should be temporary.
Where are Linux logs?
journalctl, /var/log, kernel messages, and application logs.
chmod 755 vs 644
Read permission numbers without guessing.
What is /etc?
How Linux organizes configuration, user data, runtime data, and devices.
apt vs dnf vs pacman
The core differences between major package management families.
systemctl basics
Start, stop, enable, inspect, and debug services safely.
Hyprland vs desktop environment
When a Wayland compositor is useful, and when a full desktop is a better default.
Where do dotfiles live?
How ~/.config, ~/.local/share, ~/.cache, /etc, and /usr/share differ.
Beginner questions
Clear answers before the terminology gets heavy.
Linux becomes much easier when the first mental model is accurate.
Do I need the terminal to use Linux?
Not always. Desktop Linux can be used graphically, but the terminal is the most consistent way to inspect and repair systems across distributions.
Why are there so many distributions?
Linux is modular. Different communities combine kernels, package managers, desktop environments, release policies, and defaults for different priorities.
What should I learn first?
Learn the filesystem tree, a small set of navigation and file commands, package management, permissions, and how to read logs. Those ideas make everything else easier.
Why it is structured this way
Linux favors visible parts over hidden machinery.
Files, permissions, processes, sockets, packages, and logs are exposed as tools you can inspect. That transparency is why Linux rewards patient learning.
A single tree
Everything appears under /, including mounted disks and virtual kernel views.
Composable commands
Small tools can be connected with pipes, redirection, and scripts.
Package repositories
Software is installed through signed, distribution-aware systems.
Text configuration
Many system behaviors can be inspected and versioned as plain files.
Service management
Daemons are started, supervised, and logged through consistent interfaces.
Least privilege
Users, groups, sudo, and permissions shape everyday security.