DEV Community: Asep Sayyad

What Really Happens When You Press Enter in the Linux Terminal? A Deep Dive Using the `ls` Command

Asep Sayyad — Sat, 25 Jul 2026 14:14:23 +0000

Reading Time: 10 minutes

You type ls, press Enter, and the result appears almost
instantly. But what actually happens during those few milliseconds?
This article follows the complete journey of a single Linux
command---from your keyboard to the kernel and back to your screen.

Introduction
Meet the Players
Step 1: Typing ls
Step 2: Pressing Enter
Step 3: The Shell Takes Over
Step 4: Finding the Command
Step 5: Creating a Process
Step 6: Loading into Memory
Step 7: CPU Execution
Step 8: Kernel Interaction
Step 9: Reading the File System
Step 10: Printing the Output
Complete Flow Diagram
Practical Example
Best Practices
Common Mistakes
Interesting Fact
Conclusion
Reader Question
SEO Metadata

Introduction

Every Linux user starts by running simple commands like ls, pwd, or
cd. They look simple, but Linux performs an impressive amount of work
before you see the output.

In this article, we'll use one command---ls---to understand how
the terminal, shell, kernel, CPU, RAM, and file system work together.

Meet the Players

Component Role

Terminal Collects keyboard input and displays output
Shell Interprets your command
PATH Helps locate executable programs
Kernel Core of Linux that manages hardware and system resources
CPU Executes machine instructions
RAM Holds running programs
File System Stores files and directories

Step 1: Typing `ls`

ls

The terminal receives each keystroke and echoes it to the screen.
Nothing has been executed yet.

Step 2: Pressing Enter

Pressing Enter tells the terminal that the command line is complete.

The terminal forwards:

ls

to the shell.

Step 3: The Shell Takes Over

The shell (usually Bash) examines the command.

It asks:

Is this an alias?
Is this a shell built-in?
Is this an executable program?

Since ls is an executable, it begins searching for it.

Step 4: Finding the Command

The shell checks directories listed in PATH.

echo $PATH

Example:

/usr/local/bin:/usr/bin:/bin

Eventually it finds:

/usr/bin/ls

You can verify this yourself:

which ls

Expected output:

/usr/bin/ls

Step 5: Creating a Process

The shell creates a new process.

Bash
 └── ls

The shell pauses while ls executes.

Step 6: Loading into Memory

Linux copies the executable from storage into RAM, prepares memory, and
sets up everything the program needs to run.

Step 7: CPU Execution

The CPU starts executing instructions inside ls.

Since no directory was specified, it assumes the current working
directory.

Step 8: Talking to the Kernel

Programs cannot directly access hardware or disks.

ls requests the Linux kernel to read the directory contents.

The kernel verifies permissions and safely retrieves the information.

Step 9: Reading the File System

The kernel reads metadata describing files and directories and returns
it to ls.

Step 10: Printing the Output

ls formats the information and writes it to stdout.

Example:

Documents
Downloads
Pictures
notes.txt

The terminal receives this text and displays it.

Finally, ls exits, Linux frees its resources, and Bash shows a new
prompt.

Complete Flow Diagram

Keyboard
   │
   ▼
Terminal
   │
   ▼
Shell (Bash)
   │
   ▼
Search PATH
   │
   ▼
Find /usr/bin/ls
   │
   ▼
Create Process
   │
   ▼
Load into RAM
   │
   ▼
CPU Executes
   │
   ▼
Kernel
   │
   ▼
File System
   │
   ▼
ls Formats Output
   │
   ▼
Terminal Displays Results

Practical Example

Run:

mkdir demo
touch demo/file1.txt demo/file2.txt
cd demo
ls

Expected output:

file1.txt
file2.txt

Everything described in this article happens every time you run ls,
even for this tiny example.

Best Practices

Use which to locate executables.
Explore echo $PATH to understand command lookup.
Learn the difference between the terminal, shell, and kernel.
Read command manuals using man ls.

Common Mistakes

Thinking the terminal executes commands.
Confusing Bash with the Linux kernel.
Assuming every command is built into the shell.
Forgetting that external commands run as separate processes.

Interesting Fact

Did you know? A modern Linux system can execute thousands of
short-lived processes every second, making simple commands like ls
appear almost instantaneous.

Conclusion

Although ls looks like a tiny command, it triggers an entire chain of
events involving the terminal, shell, process management, memory
allocation, CPU execution, the Linux kernel, and the file system.
Understanding this workflow builds a strong foundation for learning
Linux, system administration, and DevOps.

A Question

Which Linux command would you like to explore next---cd, pwd,
grep, or cat? Let me know in the comments!

Setting Up Docker for Multiple Applications

Asep Sayyad — Sat, 25 Jul 2026 13:00:30 +0000

After getting my free Oracle Cloud server ready, the next challenge was
running more than one application.

At first, I installed everything directly on the server. It worked, but
as I added more projects, managing everything became difficult.

That's when I started using Docker.

What Is Docker?

Docker lets you package an application with everything it needs to run.

Each application runs inside its own container, so one project doesn't
interfere with another.

Think of it as giving every application its own small workspace.

Why I Chose Docker

Docker made my server easier to manage.

It helped me:

Run multiple applications
Keep projects separated
Update applications safely
Create backups easily
Move applications to another server
Keep the server organized

My Setup

Today, my server runs different services in separate containers.

Examples include:

Personal portfolio
API services
Reverse proxy
Databases
Monitoring tools

This makes troubleshooting much easier.

Challenges I Faced

Learning Docker wasn't perfect.

Some common problems I faced were:

Port conflicts
Wrong volume mappings
Restart loops
Low memory
Network issues

Every mistake helped me understand Docker better.

Tips for Beginners

Start small.

Learn these concepts first:

Images
Containers
Volumes
Networks
Docker Compose

Once you understand these basics, everything becomes much easier.

Why Every DevOps Beginner Should Learn Docker

Docker is widely used in modern software development.

By practicing on a free cloud server, you gain real hands-on experience
instead of only watching tutorials.

That practical experience is valuable when starting a career in DevOps.

What's Next?

In the next article, I'll show how I use Nginx Proxy Manager to host
multiple domains on a single server.

Final Thoughts

Docker completely changed how I manage my server.

If you're starting your DevOps journey, learning Docker is one of the
best investments you can make.

Question for Readers

What was the first application you deployed with Docker? I'd love to
hear your experience in the comments!

Why I Chose Oracle Cloud Always Free for My Production Server

Asep Sayyad — Fri, 24 Jul 2026 14:23:29 +0000

When I wanted to host my own applications, I had one big problem---I
didn't want to pay every month for a VPS.

I was still learning Linux, Docker, and DevOps, so I wanted a place
where I could make mistakes, learn, and build real projects without
worrying about monthly costs.

That's when I found Oracle Cloud Always Free.

At first, I thought, "There must be a catch." A cloud server that stays
free forever sounded too good to be true.

After using it for my own projects, I realized it was exactly what I
needed.

Why I Didn't Choose Other Free Hosting

There are many free hosting services, but most of them have limits.

GitHub Pages is great for static websites.
Vercel is excellent for frontend applications.
Some free VPS providers only stay free for a limited time.
Many platforms don't give full control over the server.

I wanted a real Linux server where I could install anything, run Docker
containers, manage my own networking, and learn how production systems
work.

Oracle Cloud Always Free gave me that freedom.

What Oracle Cloud Always Free Gives You

With the Always Free tier, I could get:

A Linux virtual machine
SSH access
A public IP address
Block storage
Full root access
The freedom to install any software I wanted

It felt like having my own server in the cloud.

Why It Was Perfect for Learning DevOps

One of the biggest reasons I chose Oracle Cloud was the experience it
gave me.

Instead of only reading tutorials, I was able to work with real tools
like:

Linux
Docker
Reverse proxies
DNS
SSL certificates
Cloudflare
GitHub Actions
Server monitoring

These are the same technologies used by many companies.

If you're new to DevOps, building your own infrastructure is one of the
best ways to gain practical experience and confidence.

The Challenges I Faced

It wasn't always easy.

I made plenty of mistakes along the way.

Some of the challenges included:

Running everything on just 1 GB RAM
Learning Docker networking
Fixing DNS problems
Setting up SSL certificates
Configuring firewalls
Recovering from server issues

Every problem taught me something new.

Looking back, those challenges helped me learn much faster than simply
following tutorials.

Why I Still Use It

Even today, Oracle Cloud Always Free is still a great platform for:

Hosting personal projects
Learning Linux
Practicing DevOps
Building Docker applications
Running multiple websites
Experimenting without monthly costs

It may not replace a large production server, but it is more than enough
for learning and small real-world projects.

What This Series Will Cover

In this series, I'll share everything I learned while building my own
production infrastructure.

Upcoming articles include:

Building Production Infrastructure on Just 1 GB RAM
Setting Up Docker for Multiple Applications
Managing Multiple Domains with Nginx Proxy Manager
SSL Certificates with Let's Encrypt
Cloudflare Setup for Better Security
Monitoring a Low-Resource Server
Backups and Disaster Recovery
Common Problems I Faced and How I Fixed Them
What I'd Do Differently If I Started Again

Final Thoughts

Oracle Cloud Always Free gave me much more than a free server.

It gave me a place to learn, experiment, break things, fix them, and
gain real DevOps experience.

If you're just starting your DevOps journey, I highly recommend building
your own projects instead of only watching tutorials.

You'll learn much more by doing.

Next Article: Building Production Infrastructure on Just 1 GB RAM

Question for You

If you could build one project on a free cloud server today, what
would it be? Let me know in the comments!

Hello DEV! I'm Asep

Asep Sayyad — Fri, 24 Jul 2026 14:04:21 +0000

I'm Asep, a Linux and DevOps enthusiast from India.

I enjoy working with Linux servers, Docker, networking, Cloudflare, Oracle Cloud, and self-hosted applications. I like building projects, solving technical problems, and sharing what I learn along the way.

This blog is where I'll write about my real experiences, including things that worked, things that failed, and the lessons I learned from both.

Here are some topics you can expect:

Linux administration
Docker and containers
Oracle Cloud Always Free
Self-hosting applications
Networking, DNS, and reverse proxies
AI tools and automation
Open-source projects
Troubleshooting guides

I believe the best way to learn is by building real projects and solving real problems. Every challenge teaches something new, and I want to document that journey so others can learn from it too.

I'll also share updates about my open-source projects, how I build them, the problems I face, and the solutions that work.

If you're interested in Linux, DevOps, self-hosting, or automation, I hope you'll find these posts useful.

Thank you for reading, and I look forward to connecting with the DEV Community.

If you'd like to see what I'm working on, you can find me here:

Portfolio: asepsayyad007.in
GitHub: asepsayyad007 on GitHub

I'm always open to feedback, suggestions, and discussions. Feel free to connect!

What's the best self-hosted tool or service you've discovered recently?

DEV Community: Asep Sayyad

What Really Happens When You Press Enter in the Linux Terminal? A Deep Dive Using the `ls` Command

Table of Contents

Introduction

Meet the Players

Step 1: Typing ls

Step 2: Pressing Enter

Step 3: The Shell Takes Over

Step 4: Finding the Command

Step 5: Creating a Process

Step 6: Loading into Memory

Step 7: CPU Execution

Step 8: Talking to the Kernel

Step 9: Reading the File System

Step 10: Printing the Output

Complete Flow Diagram

Practical Example

Best Practices

Common Mistakes

Interesting Fact

Conclusion

A Question

Setting Up Docker for Multiple Applications

What Is Docker?

Why I Chose Docker

My Setup

Challenges I Faced

Tips for Beginners

Why Every DevOps Beginner Should Learn Docker

What's Next?

Final Thoughts

Question for Readers

Why I Chose Oracle Cloud Always Free for My Production Server

Why I Didn't Choose Other Free Hosting

What Oracle Cloud Always Free Gives You

Why It Was Perfect for Learning DevOps

The Challenges I Faced

Why I Still Use It

What This Series Will Cover

Final Thoughts

Question for You

Hello DEV! I'm Asep

Step 1: Typing `ls`