Everything you need to know about cloud computing: what it is, the deployment models, service types (IaaS, PaaS, SaaS), benefits, and what’s new in 2026. Your fun, practical starting point for the cloud.
Let’s get one thing straight right away: the cloud is not a fluffy thing in the sky storing your vacation photos next to a rainbow. It’s also not magic (though it can feel like it). The cloud is, at its core, a massive network of data centers enormous buildings packed wall to wall with servers, storage systems, and networking gear owned and operated by companies like Microsoft, Amazon, and Google, and made accessible to you and your business over the internet.
To truly appreciate the cloud, you need to understand what came before it and why it was such a headache.
Imagine you run a company. You need IT infrastructure: servers to run your apps, storage for your files, networking gear to connect everything, and a room (or whole building) to keep it all in, climate controlled, secure, and staffed by IT professionals. All of that hardware? You buy it. You maintain it. You upgrade it. You babysit it at 2am when something breaks.
Now picture this: your company runs an annual conference or a Black Friday style sales event. For two weeks a year, your systems are under enormous stress. So what do you do? You buy MORE servers to handle that peak load. Then for the other 50 weeks of the year, those expensive machines sit in a rack doing absolutely nothing useful, quietly draining your electricity budget.
Cloud computing is the on-demand delivery of computing resources including servers, storage, databases, networking, software, analytics, and intelligence over the internet, on a pay-as-you-go basis.
The key phrase here is on-demand. You don’t need to plan months ahead, order hardware, wait for delivery, and set it all up. You log in to a cloud portal, click a few buttons (or run a script), and within minutes you have a fully functional server, database, or application environment ready to go. And when you’re done? You delete it. You stop paying. That’s it.
The major cloud providers powering this revolution include:
Not all clouds are created equal. The way you deploy your cloud environment depends on your business’s needs around privacy, cost, compliance, and control.
Here’s a fun analogy: think about how you get to work every day.
Like your own car, a private cloud is dedicated exclusively to one organization. It can be hosted on-premises in your own data center, or managed off-premises by a third-party provider, but the key is: nobody else shares it. This is the go-to choice for organizations with strict compliance or regulatory requirements, think banks, hospitals, and government agencies. High control, high cost.
This is the bus. Resources are owned and managed by cloud providers and shared across multiple customers (though your data remains isolated and secure). You don’t worry about maintaining anything the cloud provider handles hardware, updates, and security infrastructure. It’s cost efficient, massively scalable, and ideal for most businesses. Services from Azure, AWS, and Google Cloud fall into this category.
The rideshare model. A hybrid cloud combines private and public cloud environments, allowing data and applications to move between them. You might keep sensitive customer data in your private cloud while running your public facing website on the public cloud. Best of both worlds and it’s the model most large enterprises are moving toward in 2026.
Less commonly discussed but equally important: a community cloud is a shared infrastructure used by a specific group of organizations with common concerns like multiple hospitals sharing a HIPAA compliant platform, or government agencies sharing a secure collaboration environment. It’s managed internally or by a third party to serve a specific community’s shared needs.
Great, so you’re using the cloud. But what exactly are you getting? Cloud services are typically broken into three layers, often visualized as a stack:
This is the raw building blocks of IT delivered over the internet. We’re talking virtual machines, storage, networking, and firewalls all provisioned on demand. You get the infrastructure; you’re responsible for everything on top of it (operating system, middleware, applications, security configuration).
Here, the cloud provider manages the infrastructure AND the underlying platform the operating system, runtime environment, patching, and scaling. You just focus on writing and deploying your code.
This is cloud computing at its most accessible. With SaaS, the provider manages absolutely everything infrastructure, platform, AND the application. You simply open a browser and use the software. No installation, no updates, no maintenance.
The cloud shifts IT spending from CapEx (capital expenditure) to OpEx (operational expenditure). Instead of buying $500,000 worth of servers that depreciate the moment they arrive, you pay for only what you consume, when you consume it. For startups and scaling businesses, this is a game changer.
Need 100 servers for an event this weekend and 5 servers next week? No problem. The cloud lets you scale up and scale down instantly, matching your resource usage to your actual demand. This is called elasticity, and it’s one of the most powerful features of modern cloud platforms.
Cloud providers operate data centers in dozens of regions around the world. This means you can deploy your applications closer to your users, reducing latency and improving performance without ever physically leaving your office.
Cloud providers invest billions of dollars annually in security infrastructure, dedicated security teams, AI powered threat detection, compliance certifications (SOC 2, ISO 27001, HIPAA, FedRAMP), and physical data center security that most organizations could never afford to replicate on their own. Your data is encrypted in transit and at rest, and access is tightly controlled.
In the old world, spinning up a new server could take weeks, procurement, delivery, setup. In the cloud, it takes minutes. This dramatically accelerates development cycles, testing, and time to market for new products and services.
Top cloud providers offer 99.9%+ uptime SLAs (Service Level Agreements), with built in redundancy across multiple data centers. If one facility has an issue, your workloads automatically fail over to another. Setting up this kind of resilience on premises would be enormously expensive.
Major cloud providers are investing heavily in renewable energy and carbon neutral operations. Microsoft has committed to being carbon negative by 2030. By moving to the cloud, organizations can reduce their own environmental footprint significantly compared to running inefficient on premises data centers.
Every major cloud provider now offers powerful, easy to consume AI services. From Azure OpenAI Service (the tech behind ChatGPT) to Google’s Vertex AI and AWS SageMaker, you can integrate cutting edge AI into your apps without a PhD in machine learning.
Functions as a Service (FaaS) platforms like Azure Functions, AWS Lambda, and Google Cloud Functions let developers run code without managing servers at all. You write the function, the cloud figures out everything else. You only pay when the code actually runs.
Not everything can (or should) live in a centralized data center. Edge computing brings processing power closer to where data is generated think IoT devices, manufacturing floors, and retail stores. Expect more hybrid edge to cloud architectures in the coming years.
The old “castle and moat” model of network security is dead. Zero Trust, the principle of “never trust, always verify,” is now the dominant security philosophy in cloud environments, especially with distributed workforces.
Most large enterprises now use services from two or more cloud providers simultaneously, avoiding vendor lock in and optimizing for specific workloads.
| IaaS | PaaS | SaaS | |
|---|---|---|---|
| You manage | OS, apps, data | Apps, data | Just data/usage |
| Provider manages | Hardware, networking | Hardware, OS, runtime | Everything |
| Analogy | Empty apartment | Furnished apartment | Hotel room |
| Example | Azure VMs | Azure App Service | Microsoft 365 |
| Best for | Full control | Fast dev | End users |
Short answer: you probably already are, whether you know it or not. Every time you use Gmail, watch Netflix, collaborate in Teams, or check your bank balance on your phone, you’re consuming cloud services.
For businesses, the question in 2026 is no longer “should we move to the cloud?” It’s “how do we move to the cloud strategically?” optimizing for cost, security, performance, and compliance.
So whether you’re just starting your cloud journey or looking to deepen your expertise, the sky isn’t the limit. The cloud is.
Want to go deeper? Explore certifications like Microsoft Azure Fundamentals (AZ-900), AWS Cloud Practitioner, or Google Associate Cloud Engineer to kickstart your cloud career.
From Bluetooth earbuds to global cloud infrastructure every connection is a network. This guide covers what a network is, the seven major types, and all key topologies with real-world examples and pros and cons for each.
A network is a collection of connected devices called nodes that share data and resources with each other. These nodes can be computers, phones, printers, servers, routers, or any hardware.
Devices connect via cables, Wi-Fi, Bluetooth, fiber optics, or cellular links. The purpose is communication, collaboration, resource sharing, and remote access.
Networks are classified by geographic reach how far they extend and how many locations they connect. From smallest to largest: PAN → LAN → CAN → MAN → WAN.
A PAN connects devices belonging to a single person, typically over 110 meters using Bluetooth or USB.
A LAN connects devices within a limited area a room, home, office, or school building using Ethernet and Wi-Fi.
A CAN connects multiple LANs across a single campus or organization university, hospital complex, or business park up to a few kilometers.
A MAN links multiple LANs or CANs across an entire city or metro area, typically over high-capacity metro fiber.
A WAN connects networks over long distances across regions, countries, or continents. The internet is the largest WAN in existence.
A VPN creates a secure, encrypted tunnel over a public network, acting as a private intermediary between your device and the destination.
A WLAN is a LAN that uses wireless connections (Wi-Fi) instead of cables, giving users mobility within the coverage area.
| Type | Range | Simple Example | Main Strength | Main Drawback |
|---|---|---|---|---|
| PAN | ~110 m | Phone + earbuds | Personal & convenient | Very short range |
| LAN | Room to building | Home Wi-Fi | Fast local sharing | Limited coverage |
| CAN | Up to a few km | University campus | Central control | Higher cost |
| MAN | City-wide | City bank branches | Urban connectivity | Provider-dependent |
| WAN | Regional to global | The internet | Worldwide reach | Higher latency |
| VPN | Any distance | Remote work access | Encrypted security | Speed overhead |
| WLAN | Room to building | Office Wi-Fi | Cable-free mobility | Interference risk |
Network topology is the arrangement of devices and connections within a network how computers, switches, routers, and links are organized, and how data flows between them.
Every device connects to a central hub or switch. The most common design in modern home and office Ethernet networks.
All devices share a single backbone cable. Historically important, less common today.
Each device connects to two neighbors forming a closed loop. Data travels around the ring to reach its destination.
Devices have multiple interconnections. A full mesh connects every node to every other; a partial mesh connects only critical paths.
A hierarchical design combining multiple star networks under higher-level switches a mix of star and bus topology.
A combination of two or more topology types. Most real-world organizational networks are hybrid because they grow and evolve over time.
A direct, dedicated link between exactly two devices the simplest topology of all.
| Topology | What it looks like | Simple Example | Main Strength | Main Weakness |
|---|---|---|---|---|
| Star | Devices around one central switch | Small office LAN | Easy management | Central switch is a single point of failure |
| Bus | Devices on one backbone cable | Older Ethernet lab | Low cabling cost | Backbone failure affects all |
| Ring | Devices form a closed loop | Industrial network | Predictable flow | Break disrupts traffic |
| Mesh | Multiple links between devices | Data center backbone | High reliability | High cost and complexity |
| Tree | Hierarchical layers of stars | Enterprise campus | Organized & scalable | Upper-level failures cascade |
| Hybrid | Mix of topologies | Multi-floor office | Flexible | Complex to manage |
| Point-to-Point | Direct link between 2 devices | Leased WAN link | Simple & reliable | Not scalable |
From Bluetooth earbuds to global cloud infrastructure every connection is a network. This guide covers what a network is, the seven major types, and all key topologies with real-world examples and pros and cons for each.
A network is a collection of connected devices called nodes that share data and resources with each other. These nodes can be computers, phones, printers, servers, routers, or any hardware.
Devices connect via cables, Wi-Fi, Bluetooth, fiber optics, or cellular links. The purpose is communication, collaboration, resource sharing, and remote access.
Networks are classified by geographic reach how far they extend and how many locations they connect. From smallest to largest: PAN → LAN → CAN → MAN → WAN.
A PAN connects devices belonging to a single person, typically over 110 meters using Bluetooth or USB.
A LAN connects devices within a limited area a room, home, office, or school building using Ethernet and Wi-Fi.
A CAN connects multiple LANs across a single campus or organization university, hospital complex, or business park up to a few kilometers.
A MAN links multiple LANs or CANs across an entire city or metro area, typically over high-capacity metro fiber.
A WAN connects networks over long distances across regions, countries, or continents. The internet is the largest WAN in existence.
A VPN creates a secure, encrypted tunnel over a public network, acting as a private intermediary between your device and the destination.
A WLAN is a LAN that uses wireless connections (Wi-Fi) instead of cables, giving users mobility within the coverage area.
| Type | Range | Simple Example | Main Strength | Main Drawback |
|---|---|---|---|---|
| PAN | ~110 m | Phone + earbuds | Personal & convenient | Very short range |
| LAN | Room to building | Home Wi-Fi | Fast local sharing | Limited coverage |
| CAN | Up to a few km | University campus | Central control | Higher cost |
| MAN | City-wide | City bank branches | Urban connectivity | Provider-dependent |
| WAN | Regional to global | The internet | Worldwide reach | Higher latency |
| VPN | Any distance | Remote work access | Encrypted security | Speed overhead |
| WLAN | Room to building | Office Wi-Fi | Cable-free mobility | Interference risk |
Network topology is the arrangement of devices and connections within a network how computers, switches, routers, and links are organized, and how data flows between them.
Every device connects to a central hub or switch. The most common design in modern home and office Ethernet networks.
All devices share a single backbone cable. Historically important, less common today.
Each device connects to two neighbors forming a closed loop. Data travels around the ring to reach its destination.
Devices have multiple interconnections. A full mesh connects every node to every other; a partial mesh connects only critical paths.
A hierarchical design combining multiple star networks under higher-level switches a mix of star and bus topology.
A combination of two or more topology types. Most real-world organizational networks are hybrid because they grow and evolve over time.
A direct, dedicated link between exactly two devices the simplest topology of all.
| Topology | What it looks like | Simple Example | Main Strength | Main Weakness |
|---|---|---|---|---|
| Star | Devices around one central switch | Small office LAN | Easy management | Central switch is a single point of failure |
| Bus | Devices on one backbone cable | Older Ethernet lab | Low cabling cost | Backbone failure affects all |
| Ring | Devices form a closed loop | Industrial network | Predictable flow | Break disrupts traffic |
| Mesh | Multiple links between devices | Data center backbone | High reliability | High cost and complexity |
| Tree | Hierarchical layers of stars | Enterprise campus | Organized & scalable | Upper-level failures cascade |
| Hybrid | Mix of topologies | Multi-floor office | Flexible | Complex to manage |
| Point-to-Point | Direct link between 2 devices | Leased WAN link | Simple & reliable | Not scalable |
The ls command short for list is the first command most people learn on Linux. It shows you what’s inside a directory. This guide takes you from the basics all the way to exploring the root filesystem and /etc/ with real simulated terminal output.
ls stands for list. It prints the names of files and directories inside a folder. Run it with no arguments and it lists your current working directory. Pass a path and it lists that path instead.
ls # list current directory ls /path/to/dir # list a specific path ls ~ # list your home directory (~ = home)
ls followed by Enter. You’ll see the contents of wherever you are right now.
Flags change how ls behaves. You can combine them freely. Here are the most important ones:
| Flag | Long form | What it does |
|---|---|---|
| -a | –all | Show hidden files (names starting with .) |
| -l | Long format permissions, owner, size, date | |
| -h | –human-readable | Human-readable sizes (4.0K, 12M) requires -l |
| -1 | One entry per line (the number 1, not letter L) | |
| -t | Sort by modification time, newest first | |
| -r | –reverse | Reverse the sort order |
| -R | –recursive | List all subdirectories recursively |
| -S | Sort by file size, largest first | |
| -F | –classify | Append type indicators (/ for dirs, * for executables) |
| -i | –inode | Show inode numbers |
| -d | –directory | List directories themselves, not their contents |
ls -la # long format + show hidden files ls -lh # long format + human-readable sizes ls -ltr # long format + sorted by time, oldest first ls -lAh # long format + all (except . and ..) + human sizes ls -1 # one item per line, clean for piping
Many Linux systems define shell aliases so you don’t have to type the full flags every time:
alias ll='ls -lh' # long + human-readable alias la='ls -lAh' # long + all hidden + human-readable alias l='ls -1' # one per line
man ls for the complete reference. Press q to exit. You can also combine ls with pipes: ls /etc | grep ssh
The root directory / is the top of the entire Linux filesystem. Everything lives inside it. Running ls / gives you the Filesystem Hierarchy Standard (FHS) the standardised layout used by all major Linux distributions.
$ ls /
bin boot dev etc home lib lib64 media mnt opt
proc root run sbin srv sys tmp usr var
Here is what each top-level directory does:
| Directory | Purpose |
|---|---|
| /bin | Essential user binaries (ls, cp, mv, bash, etc.) |
| /sbin | System administration binaries (only root typically uses these) |
| /etc | System-wide configuration files the most important directory |
| /home | Personal directories for each user (/home/username) |
| /var | Variable data logs (/var/log), databases, mail spools |
| /dev | Device files (hard drives, USB, terminals everything is a file) |
| /proc | Virtual filesystem live kernel and process information |
| /sys | Virtual filesystem hardware and kernel subsystem info |
| /tmp | Temporary files, cleared on reboot |
| /boot | Bootloader and kernel images |
| /usr | User programs, libraries, and documentation |
| /root | Home directory for the root user (not /home/root) |
| /run | Runtime data since last boot (PIDs, sockets) |
| /lib | Shared libraries needed by /bin and /sbin |
| /mnt | Mount point for temporarily mounted filesystems |
| /opt | Optional/add-on software packages |
$ cd /
$ pwd
/
Now run ls -lh from here to see the root directory in long format with human-readable sizes:
$ ls -lh
total 72K
lrwxrwxrwx 1 root root 7 Apr 1 2024 bin -> usr/bin
drwxr-xr-x 4 root root 4.0K Jan 15 08:22 boot
drwxr-xr-x 19 root root 3.8K Apr 3 10:01 dev
drwxr-xr-x 133 root root 12K Apr 3 09:55 etc
drwxr-xr-x 3 root root 4.0K Mar 29 18:42 home
lrwxrwxrwx 1 root root 7 Apr 1 2024 lib -> usr/lib
drwx------ 2 root root 16K Mar 28 11:00 lost+found
drwxr-xr-x 2 root root 4.0K Mar 28 11:00 media
drwxr-xr-x 2 root root 4.0K Mar 28 11:00 mnt
drwxr-xr-x 5 root root 4.0K Apr 1 10:35 opt
dr-xr-xr-x 220 root root 0 Apr 3 10:01 proc
drwx------ 5 root root 4.0K Apr 3 11:30 root
drwxr-xr-x 30 root root 840 Apr 3 10:01 run
lrwxrwxrwx 1 root root 8 Apr 1 2024 sbin -> usr/sbin
drwxr-xr-x 2 root root 4.0K Apr 1 2024 srv
dr-xr-xr-x 13 root root 0 Apr 3 10:01 sys
drwxrwxrwt 12 root root 4.0K Apr 3 11:28 tmp
drwxr-xr-x 14 root root 4.0K Apr 1 2024 usr
drwxr-xr-x 12 root root 4.0K Apr 1 10:35 var
cd ~ takes you back to your home directory. cd - takes you back to the previous directory. pwd always shows you where you are.
Now that you are in /, let’s experiment with different flag combinations. This is where most beginners learn what each flag actually does by seeing real output.
$ ls -1
bin
boot
dev
etc
home
lib
lib64
media
mnt
opt
proc
root
run
sbin
srv
sys
tmp
usr
var
The -1 flag (the digit 1) forces one item per line clean and easy to pipe into grep, wc, or other tools.
$ ls -1 -h
bin
boot
dev
etc
home
lib
lib64
media
mnt
opt
proc
root
run
sbin
srv
sys
tmp
usr
var
-h flag (human-readable sizes) has no effect without -l. Sizes only appear in long format. To see sizes, use ls -1lh instead.
$ ls -a
. .. bin boot dev etc home lib lib64
media mnt opt proc root run sbin srv
sys tmp usr var
The -a flag reveals hidden items those whose names begin with a dot. Every directory has . (current directory) and .. (parent directory) as special hidden entries. The real / on most systems has almost no other hidden files, but home directories have many (like .bashrc, .ssh/, .gitconfig).
$ ls --all
. .. bin boot dev etc home lib lib64
media mnt opt proc root run sbin srv
sys tmp usr var
-a and --all are identical. Short flags are faster to type; long flags are more readable in scripts.
/etc/ is the most important configuration directory on a Linux system. Every major service networking, SSH, DNS, package management, user accounts stores its configuration files here.
$ ls -1 /etc/
adduser.conf
alternatives/
apt/
bash.bashrc
ca-certificates.conf
cron.d/
cron.daily/
cron.hourly/
cron.monthly/
cron.weekly/
crontab
default/
environment
fstab
grub.d/
group
gshadow
hostname
hosts
init.d/
inputrc
issue
locale.gen
logrotate.conf
logrotate.d/
lsb-release
machine-id
motd
network/
nsswitch.conf
os-release
pam.d/
passwd
profile
profile.d/
protocols
resolv.conf
security/
services
shadow
shells
ssh/
ssl/
sudoers
sudoers.d/
sysctl.conf
sysctl.d/
systemd/
timezone
udev/
vim/
X11/
Here are the most important files and directories in /etc/:
| Path | Purpose |
|---|---|
| /etc/passwd | User account database (username, UID, home, shell) |
| /etc/shadow | Encrypted user passwords (root-readable only) |
| /etc/group | Group definitions |
| /etc/sudoers | Who can run sudo and with what permissions |
| /etc/fstab | Filesystem mount table auto-mounts at boot |
| /etc/hostname | The machine’s hostname |
| /etc/hosts | Static hostname-to-IP mappings |
| /etc/resolv.conf | DNS resolver settings |
| /etc/ssh/ | SSH server and client configuration |
| /etc/systemd/ | Systemd service definitions and overrides |
| /etc/apt/ | APT package manager configuration (Debian/Ubuntu) |
| /etc/cron.d/ | System cron jobs |
| /etc/profile | System-wide shell environment settings |
| /etc/os-release | OS identity (name, version, ID) |
-h only affects the size column in -l (long format). Without -l, there is no size column to format, so -h silently does nothing. Use ls -lh /etc/ to see sizes.
ls -la /etc/ # full details including hidden files ls /etc/ | grep ssh # find SSH-related configs ls -lh /etc/ssh/ # detailed view of SSH config dir cat /etc/os-release # show current OS version cat /etc/hostname # show the machine hostname
ls -lh /etc/ssh/ to see SSH configs, ls /etc/apt/ for package manager settings, or ls -la ~ to see all the hidden dot-files in your home directory.
Before you touch a single VM or config file, you need to understand what the shell is telling you, how every Linux command is built, and where the system keeps its configuration. This guide covers it all.
Proxmox Virtual Environment (PVE) is a free, open-source, enterprise-grade server virtualization platform built on Debian Linux. It combines two powerful virtualization technologies into one browser-managed solution:
You manage everything from a clean web interface at https://YOUR-IP:8006. The current version (9.x) runs on Debian 13 (Trixie) with Linux kernel 6.17+, is free under AGPLv3, and is a popular cost-effective alternative to VMware vSphere.
When you open a terminal or SSH into a Proxmox server, the shell prompt gives you two critical pieces of information at a glance: who you are and where you are in the filesystem.
user@pve:~$
The dollar sign means you are logged in as a regular user with limited privileges. Most Proxmox management commands will fail or require sudo from this prompt.
user@pve:~$ ls /etc # Works fine user@pve:~$ apt update # Permission denied user@pve:~$ sudo apt update # Works with sudo
root@pve:~#
The hash sign means you are root full, unrestricted system access. No sudo needed. This is the default on a fresh Proxmox install and what every official guide assumes.
root@pve:~# apt update && apt full-upgrade -y root@pve:~# qm start 100 root@pve:~# zpool status
The tilde in your prompt shows you are in your home directory. It is also a shortcut in any command. As root, ~ = /root. As a regular user, ~ = /home/username.
cd ~ # Jump to home from anywhere cd ~/backups # Navigate to a subfolder of home ls ~ # List home directory contents nano ~/.bashrc # Edit your Bash configuration
| Symbol | Meaning | Privilege | Home Path |
|---|---|---|---|
| $ | Regular user prompt | Limited needs sudo | /home/username |
| # | Root user prompt | Full administrator | /root |
| ~ | Home directory shortcut | Depends on current user |
Every Linux command follows the same universal three-part pattern. Learn this once and any new tool becomes easier to understand.
command [options] [arguments]
The command is the program to run. Options modify its behaviour short with one dash (-y), long with two (--yes). Arguments are the specific targets it acts on a VM ID, file path, hostname, etc.
# command: ls | option: -1 | argument: /etc root@pve:~# ls -1 /etc # command: qm | sub-command: start | argument: 101 root@pve:~# qm start 101 # command: apt | sub-command: upgrade | option: -y root@pve:~# apt upgrade -y
root@pve:~# qm create 101 \ --name "UbuntuServer" \ --memory 4096 \ --cores 2 \ --net0 virtio,bridge=vmbr0 \ --scsi0 local-lvm:32
qm shutdown 101 --timeout 60 # Shutdown VM with timeout pct create 201 local:vztmpl/debian-12-standard_12.0-1_amd64.tar.zst \ --hostname debian-ct --memory 1024 # Create container pvesm list local-zfs # List storage contents pvecm status # Check cluster status
--memory not -m) in scripts they are self-documenting. Quote values with spaces: --name "My VM". Press Tab for auto-completion. Run man qm or qm --help when stuck.
/etc is the central home for system-wide configuration files in any Linux system. Every major service networking, SSH, DNS, package management, user accounts stores its settings here. In Proxmox, it also holds all VM, container, and cluster definitions.
root@pve:~# cd /etc root@pve:/etc#
Notice the prompt updates from ~ to /etc once inside. Useful navigation commands:
cd /etc # Go to /etc from anywhere pwd # Confirm your location cd - # Go back to the previous directory cd ~ # Return to home (/root as root)
root@pve:~# ls -1 /etc
The -1 flag (the number one, not the letter L) prints one entry per line clean and easy to pipe into grep.
ls -1 /etc # One per line ls -la /etc # Detailed: permissions, sizes, dates ls /etc | grep ssh # Find SSH-related configs ls -1 /etc/pve/ # Explore the Proxmox config folder
| Path | Purpose |
|---|---|
| /etc/hostname | The server’s hostname |
| /etc/hosts | Static hostname-to-IP mappings |
| /etc/resolv.conf | DNS resolver settings |
| /etc/fstab | Filesystem mount table |
| /etc/ssh/sshd_config | SSH server configuration |
| /etc/network/interfaces | Network config bridges, bonds, VLANs |
| /etc/apt/sources.list.d/ | APT repository definitions |
| /etc/pve/ | Proxmox cluster filesystem all VM/CT configs, storage, user data |
| /etc/pve/storage.cfg | Storage pool definitions |
| /etc/pve/datacenter.cfg | Global Proxmox settings |
cat /etc/pve/storage.cfg # View storage definitions cat /etc/network/interfaces # View network config cat /etc/os-release # View OS and kernel version ls /etc/apt/sources.list.d/ # Check APT repositories
cp /etc/network/interfaces /etc/network/interfaces.bak
# prompt means root access. The ~ shortcut means home directory. Every command follows command [options] [arguments]. And /etc is where Linux keeps all its configuration. Master these four things and no Proxmox guide or man page will feel foreign.
From a Finnish student’s hobby project in 1991 to the invisible backbone of the modern internet. Here is the history of Linux, how it works, where it runs, and why every engineer should understand it.
The story of Linux begins in 1991 with a Finnish computer science student named Linus Torvalds. Frustrated with the limitations of MINIX a Unix-like teaching OS that could not be freely modified he announced on a Usenet mailing list that he was building a “free operating system (just a hobby, won’t be big and professional like GNU).” That hobby became one of the most consequential pieces of software ever written.
Torvalds released the first Linux kernel (version 0.01) in September 1991. Just 10,000 lines of code but it was free, open, and built on solid Unix principles. Combined with the GNU Project’s user-space tools that Richard Stallman’s team had been assembling since 1983, the two together formed the world’s first fully free, Unix-like operating system: GNU/Linux.
Through the 1990s, Linux grew explosively. The internet era created enormous demand for stable, free server software. Companies like Red Hat commercialized it, universities taught it, and a global developer community contributed patches. By the early 2000s, Linux was the backbone of the web. By 2026, the stable kernel sits at version 6.19+, maintained by thousands of contributors worldwide.
At its core, Linux is a monolithic kernel a single privileged program that manages the CPU, memory, file systems, device drivers, and networking for everything running above it. Unlike proprietary systems, every line of that kernel is publicly readable, auditable, and modifiable under the GNU GPL license.
This openness gave rise to distributions complete operating systems built on top of the Linux kernel, packaged with GNU tools, a desktop environment, a package manager, and thousands of applications. Ubuntu, Fedora, Debian, Arch, and hundreds of others each make different trade-offs between stability, cutting-edge features, simplicity, and customization.
Linux’s dominance is quiet but absolute:
Linux inherits the Unix philosophy write small programs that do one thing well, compose them via pipes, treat everything as a file, and favor transparency over magic. This is why a single Bash one-liner can chain grep, awk, sort, and uniq to process millions of log lines more efficiently than many GUI tools ever could.
It is also why Linux scales: the same kernel powering a Raspberry Pi also powers a 10,000-core HPC cluster. Loadable kernel modules let drivers be added or swapped without recompiling the whole system. The eBPF subsystem lets you safely extend kernel behavior at runtime enabling powerful observability and networking tools without touching kernel code directly.
cat /var/log/syslog | grep "error" | sort | uniq -c | sort -rn
The Linux kernel continues its rapid release cadence a new mainline version roughly every two to three months. Key focus areas in 2026 include:
The most popular distribution, Ubuntu 26.04 LTS, ships with GNOME 50, full Wayland-by-default sessions, and TPM-backed disk encryption a signal of how far the Linux desktop has matured.
For software engineers, Linux is not just an OS choice it is the foundation of the modern software stack. Containers (Docker, Kubernetes) are built on Linux kernel primitives:
cgroups # Resource limits per process group namespaces # Isolation: PID, net, mount, user seccomp # Syscall filtering for sandboxing
Most CI/CD pipelines run on Linux. Most production systems you deploy to run Linux. Understanding the kernel how the scheduler allocates CPU time, how mmap manages virtual memory, how system calls cross the user/kernel boundary directly translates to writing faster, more reliable software.
Before your first commit, Git needs to know who you are. Here is how to set your global username and email, verify them, and make sure your commits are linked to your account.
Run the following command, replacing the example name with your actual name:
git config --global user.name "Your Name"
Verify it was set correctly:
git config --global user.name
Run the following command, replacing the example address with your actual email:
git config --global user.email "your-email@example.com"
Verify it was set correctly:
git config --global user.email
You can run both commands back to back to set up your identity in one go:
git config --global user.name "Your Name" git config --global user.email "your-email@example.com"
To see your full Git configuration at once:
git config --global --list