Miron Blog

Linux

a plain-language explainer

Linux is the quiet, sturdy operating system that runs most of the world's servers — and something very close to it lives inside your Mac and your Android phone too. You only need a little of it to work confidently: the idea that files belong to users with permissions, and a small handful of typed commands for moving around and looking at things.

You may think you’ve never touched Linux. But if you’ve used an Android phone, or a Mac, you’ve been standing on its close cousins the whole time. Underneath their friendly screens lives the same family of plumbing — the same ideas about files, users, and commands. Learning a little Linux isn’t learning something foreign; it’s learning the shape of the ground you’ve already been walking on.

And the good news, the genuinely reassuring news, is this: you do not need to master Linux. For most modern work — running a server, deploying a website, letting an AI help you build things — you need just a small, friendly handful of ideas and commands. That’s what this page is.

The one big idea: users and permissions

Picture a shared house. Everyone who lives there has their own room, with their own things, and a key to their own door. You can do as you like in your own room, but you can’t just walk into a housemate’s room and rearrange their shelves — you don’t have the key.

A Linux computer is exactly that house. Every file belongs to someone — a user — and each file carries little rules, called permissions, about who’s allowed to read it, change it, or run it. This is why, sometimes, the computer politely tells you “you can’t do that” — you’re reaching for a door you don’t hold the key to. It isn’t broken; it’s being careful.

And what’s “sudo”? The master key.

Sometimes you genuinely need to do something that touches the whole house — installing software for everyone, changing a shared setting. For those moments there’s a master key, and its name is sudo. You put it in front of a command to say “do this with full authority”:

sudo something

It will usually ask for your password, because a master key deserves a moment’s pause. The gentle wisdom here: only reach for sudo when a command truly needs it. Most of your daily work happens comfortably in your own room, no master key required.

The small handful of commands that carry you

The command line is just a place where you type an instruction and press Enter, instead of clicking. It looks bare at first, but it’s only a conversation: you say a short word, the computer does the thing. Here are the ones that carry you through most days — each is a single small word:

  • ls — list: show me what’s in this folder.
  • cd — change directory: move me into a folder.
  • cat — show me the contents of a file.
  • mkdir — make a new folder.
  • nano — open a simple editor to change a file.

ls and cd are the two you’ll use most — they’re how you walk around. Try the simplest, safest one right now; it just lists what’s around you and changes nothing:

ls

Then cd foldername steps you inside a folder, and cd .. steps you back out. That’s most of navigation, right there.

A few more, for when you need them — including a cleanup gem
  • du — disk usage: how much space is this using?
  • ncdu — a friendlier, visual version of du, wonderful for cleanup.
  • chown — change who owns a file.
  • chmod — change a file’s permissions (its read/write/run rules).

ncdu deserves a special mention: when your disk is mysteriously full, you run it and it draws you a clear, navigable picture of what’s eating your space, biggest first. It has rescued many an afternoon. (You may need to install it once; it’s small and worth it.) Once it’s installed, this single word opens that picture:

ncdu

chown and chmod are simply the tools for changing the ownership and permissions we talked about above — the “who holds the key” settings. You’ll meet them occasionally, often when something says “permission denied” and you need to adjust who’s allowed in.

Why a little of this unlocks so much

Here’s the quiet payoff. These same ideas — users, permissions, and that small vocabulary of commands — are the same everywhere. The Linux on a faraway server, the Terminal on a Mac, the inside of an Android phone: they speak this shared language. Learn it a little on your own laptop, in tiny daily doses, and it becomes muscle memory — and then it carries over, unchanged, to every server you’ll ever touch.

It’s also the doorway to a few bigger tools that each deserve their own telling — connecting to other computers, running little self-contained machines, installing project pieces. Those build directly on the ground you’ve just stood on here.

So, in one breath

Linux is the sturdy foundation under most servers — and under your Mac and Android too — and you need only a little of it: the idea that files belong to users with permissions, the occasional master key of sudo, and a small, friendly set of typed commands like ls and cd that, once they’re in your fingers, work the same way everywhere you go.