Linux Architecture

If you’ve ever opened a terminal, typed a command, and wondered what actually happens behind the scenes — this article is for you. We’ll break down Linux architecture layer by layer, in the simplest way possible.

1. What is Linux?

Linux is an operating system kernel.

In simple words: Linux helps software communicate with computer hardware.

For example, when you open a file, this is roughly what happens:

You
 ↓
Application
 ↓
Linux
 ↓
Hard Disk

Linux tells the computer what to do.

You’ve probably heard of operating systems built on top of Linux — these are called distributions (distros):

• Ubuntu
• Kali Linux
• Debian
• Fedora
• Arch Linux

2. The Layers of Linux Architecture

Linux can be understood as a stack of layers, each one talking to the layer below it:

     👤 USER
           ↓
    APPLICATIONS
           ↓
      SHELL / GUI
           ↓
    SYSTEM LIBRARIES
           ↓
     SYSTEM CALLS
           ↓
        KERNEL
           ↓
       HARDWARE

Let’s go through each one.

3. Hardware 🖥️

Hardware refers to the physical parts of your computer:

• CPU
• RAM
• Hard Disk / SSD
• Keyboard
• Mouse
• Network Card
• USB
• Monitor

HARDWARE
   ┌─────────────────┐
   │ CPU             │
   │ RAM             │
   │ SSD             │
   │ Network Card    │
   └─────────────────┘

Linux controls all of these hardware components — through the kernel.

4. Kernel ❤️

The kernel is the most important part of Linux. Think of it as the manager of the entire system.

It manages:

• CPU
• RAM
• Files
• Hardware
• Network
• Processes
• Security

For example:

Application
     ↓
   Kernel
     ↓
   CPU/RAM

The application asks the kernel, “I need CPU and memory,” and the kernel handles the request.

Simple definition: The kernel is the core of Linux that manages hardware and system resources.

5. Shell 🐚

A shell lets you communicate with Linux using commands. For example:

ls
cd Documents
mkdir test

The shell understands these commands and tells Linux to execute them.

Get Kinza’s stories in your inbox

Join Medium for free to get updates from this writer.

Remember me for faster sign in

Common shells include:

• Bash
• Zsh
• Fish

The flow looks like this:

YOU
 ↓
SHELL
 ↓
LINUX KERNEL
 ↓
HARDWARE

6. Terminal vs Shell

These two terms are often mixed up, but they’re different things.

Terminal — the window where you type commands.

Shell — the program that interprets and understands your commands.

Terminal
   ↓
Bash
   ↓
Linux Kernel

Simple way to remember it:

Terminal = the place where you type. Shell = the program that understands what you typed.

7. Applications

Applications are the programs you actually use day to day:

• Firefox
• VLC
• Wireshark
• VS Code
• LibreOffice
• Nmap

Here’s what happens when you open one:

You open Firefox
       ↓
Firefox asks Linux
       ↓
Linux gives CPU + RAM
       ↓
Firefox runs

8. System Calls 📞

This sounds technical, but it’s actually simple.

A system call is how a program asks the kernel to do something for it. For example, if a program wants to read a file:

Program
   ↓
"Kernel, please read this file"
   ↓
System Call
   ↓
Kernel
   ↓
File

Some common system calls:

open()
read()
write()
close()

You don’t type these directly in the terminal — programs use them internally.

9. System Libraries

Libraries contain ready-made functions that programs can reuse instead of writing everything from scratch.

Application
     ↓
Library
     ↓
System Call
     ↓
Kernel

One of the most important Linux libraries is glibc. You don’t need to memorize every library right now — just know that this layer exists between applications and system calls.

10. Process

A process is simply a running program.

For example, when you open Firefox:

Firefox program
      ↓
Running Firefox
      ↓
Process

Every process gets a number called a PID (Process ID). For example:

Firefox → PID 1234

You can view running processes using:

ps

or:

top

11. Memory Management 🧠

The kernel is also responsible for managing RAM.

Suppose your computer has 8 GB of RAM, and you open:

Firefox
VS Code
Wireshark
Terminal

All of these programs need memory. So the kernel has to decide: which program gets how much memory?

Programs
   ↓
Kernel
   ↓
RAM

Wrapping Up

That’s the full picture — from the moment you type a command, to the shell interpreting it, to system calls reaching the kernel, and finally the kernel talking to your hardware. Once you see Linux as a stack of layers working together, the whole system stops feeling mysterious and starts making a lot more sense.

If you’re just starting out with Linux, try opening a terminal right now and run ps or top — you'll actually see these concepts in action.

If you found this useful, follow for more beginner-friendly breakdowns of Linux, cybersecurity, and systems concepts.