Iβve started learning Linux, and I just completed my first week.
Before this, I had used Linux mainly through the terminal for coding and development. But this week, I decided to slow down and understand what Linux actually is, where it came from, how it works, and how its different parts connect together.
Hereβs what I learned during Week 1.
π§ What is Linux?
One of the first things I learned is that Linux is technically a kernel, not an operating system by itself.
The kernel is the core part of a system that communicates with the computer's hardware and manages important resources such as:
- CPU
- Memory
- Storage
- Devices
- Processes
The Linux kernel works together with other software to create a complete operating system.
For example, distributions such as Ubuntu, Debian, Fedora, and Arch Linux use the Linux kernel together with other tools and software.
This distinction was one of the first things that really changed how I understood Linux.
π§ What is a Kernel?
The kernel acts as a bridge between hardware and software.
A simple way I understand it is:
Applications β Operating System β Kernel β Hardware
When an application needs something from the computer, the kernel helps manage access to the hardware.
For example, when a program needs to:
- read a file
- use memory
- communicate with a device
- create a process
the kernel helps make that possible.
π» What is an Operating System?
I also learned that an Operating System (OS) is much bigger than the kernel.
An operating system provides the environment that allows users and applications to interact with the computer.
Examples include:
- Linux-based operating systems
- Windows
- macOS
- Android
- iOS
A Linux distribution combines the Linux kernel with many other components to provide a usable operating system.
π A Little History of Linux
Linux has an interesting history.
The Linux kernel was created by Linus Torvalds in 1991 while he was a student.
It was inspired by the Unix operating system, but Linux was developed as a free and open-source project.
Over time, developers around the world contributed to the project, and Linux grew into one of the most important technologies in modern computing.
Today, Linux is used in many places, including:
- Servers
- Cloud infrastructure
- Supercomputers
- Embedded systems
- Networking equipment
- Android devices
- Development environments
Learning this history helped me understand why Linux is so important in technology today.
π How the Pieces Connect
One of the most useful things I learned this week was understanding how the different components fit together.
A simplified view is:
User β Applications β Shell β Kernel β Hardware
For example, when I type a command into the terminal:
- I enter the command.
- The shell interprets the command.
- The operating system requests the necessary resources.
- The kernel communicates with the hardware.
- The result is returned to me.
This made the Linux terminal feel less mysterious.
β¨οΈ Linux Basics
I also spent time getting comfortable with basic Linux concepts and terminal commands.
Some of the commands I worked with include:
pwd
ls
cd
mkdir
touch
cp
mv
rm
cat
less
clear
These commands may look simple, but they are building blocks for becoming comfortable with the Linux command line.
I'm learning that Linux isn't just about memorizing commands.
It's more important to understand what each command does, why you are using it, and how commands can work together.
π§© What I Learned
My biggest takeaway from Week 1 is that Linux is not just a terminal or a collection of commands.
There is a whole system underneath what I see on the screen.
I now have a better understanding of:
- What Linux is
- What the Linux kernel does
- What an operating system is
- The relationship between hardware and software
- The difference between Linux and a Linux distribution
- The basic history of Linux
- How the shell, kernel, and hardware interact
- Basic Linux terminal commands
π What's Next?
This is only Week 1, so there is still a lot to learn.
In the coming weeks, I want to become more comfortable with:
- File systems
- Permissions
- Users and groups
- Processes
- Package management
- Networking
- Shell scripting
- System administration
- Troubleshooting
I'm documenting this journey because I believe learning in public is a great way to track progress, reinforce what I learn, and hopefully help someone else who is starting from zero.
Week 1: Foundation built. π§
Now, on to Week 2.
Top comments (0)