Every Core LINUX Concepts Explained in 5 Minutes

Here are 10 concepts that explain how Linux actually works. Number one, the kernel. Linux itself is technically the kernel, the core layer that sits between your programs and the hardware. Programs cannot directly control the processor, read from a disk, or send data over the network. Everything goes through the kernel, which decides which program gets CPU time, memory, disk access, and network access. Number two, the terminal and the shell. The terminal is the window where you type and see output. The shell is the program inside that window that understands what you typed. Bash, ZSH, and Phish are shells. When Linux says, command not found, it does not mean the command could never exist. It means the shell searched every folder listed in path and could not find the program there. Number three, everything is treated like a file. Linux exposes devices, processes, and system information through file-like paths. Instead of creating completely different interfaces for each one. Storage devices appear inside slash dev. Information about running processes appears inside slash proc. Hardware details appear through slash sys. The point is that Linux lets programs interact with many different parts of the system using the same read and write operations they already use on files. Number four, users, permissions, root, and sudo. Every file has an owner, a group, and permissions that control who can access it. The three basic permissions are read, write, and execute. Read lets you view the contents. Write lets you make changes. Execute lets you run the file as a program. These apply separately for the owner, the group, and everyone else. Root is the most powerful user. Root can change settings, install software, and bypass most normal permission checks. That is why most people use sudo instead. Sudo allows an approved user to run one command with elevated privileges without permanently working as root. Number five, programs, processes, and services. A program is code stored on the machine. A process is that program while it is running. Every process gets a process ID so Linux can keep track of it. Processes also run as specific users, which means the same permission rules apply. Some processes run in the background as services. A web server, database, or SSH server can run as a service. On most modern Linux systems, services are managed by systemd. Starting and enabling a service are not the same thing. Starting runs it right now. Enabling tells the system to start it on every boot. Number six, input, output, and pipes. A command normally receives input from your keyboard and sends output to the terminal. You can change that. You can send output into a file, read from a file as input, or connect one command directly to another using a pipe. Instead of searching for one special command that solves your exact problem, you combine small commands that already exist. One lists things. Another filters. Another counts. Each one does a single job and pipes connect them. Number seven, package managers. A package manager finds the application, downloads everything it needs, installs it, and keeps track of updates. Ubuntu and Debian use apt. Fedora uses dnf. Arch uses pacman. These tools pull from repositories maintained for the distribution, which is generally safer than downloading from random websites. Number eight, logs. When something breaks, one of the first places to look is the logs. On systemd systems, use journalctl. Other log files sit under slashvar slash log. What do the logs say? Number nine, networking and SSH. An IP address identifies a machine on a network. DNS converts names into IP addresses. A port identifies a particular service running on that machine. The IP address gets you to the right computer. The port gets you to the right service on it. SSH gives you secure command-line access to another machine. You can read logs, restart services, install software, and fix problems remotely. Number ten, containers. A container packages an application with exactly what it needs, kept separate from everything else on the machine. Containers share the host's Linux kernel, which is why they are much smaller and start much faster than virtual machines. Under the hood, Linux namespaces and cgroups provide that isolation. Tools like Docker and Podman make them easy to work with. Now go back to that command from the start. The terminal shows what you typed. The shell interprets it and searches path for the program. Linux checks your user and your permissions. The kernel creates a process and gives it the resources it needs. The program may read files, pass its output into another command, use the network, run as a service, or even run inside a container. If something fails, the logs are usually the best place to understand why. That is when Linux stops feeling like a collection of random commands and starts making sense as a system. Linux is not difficult. It is usually just taught in the wrong order.