Ln

Alright, let’s get into the weeds. You’ve probably heard the term “inode” thrown around and maybe nodded along without really getting it. That’s fine. Everyone does at first. But if you want to truly understand how your system handles files—especially when we talk about links—you need to wrap your head around this concept. It’s the secret sauce, and it’s actually pretty elegant once the scales fall from your eyes. Think of a file on your disk not as a single, monolithic thing, but as being split into two parts.

Right, let’s talk about links. No, not the “save the princess” kind. The kind that saves you from having to make a dozen copies of the same file all over your filesystem, wasting precious disk space and your sanity. We’re talking about hard links and symbolic (or soft) links. The ln command is your tool here, and it’s deceptively simple. The difference between ln and ln -s is the difference between a clone and a shortcut, and getting it wrong can lead to some properly confusing situations.

Alright, let’s talk about digital demolition. You’re going to spend a significant part of your computing life deleting things. It’s cathartic. It’s also, in the world of the command line, terrifyingly permanent. This isn’t your GUI trash can with a satisfying undo. This is rm, and it takes no prisoners. My job is to make sure you don’t end up as a cautionary tale. The core tools are simple: rm (remove) for files and rmdir (remove directory) for, you guessed it, directories. The how is trivial. The why and the how-not-to-erase-your-entire-home-directory are what we’re here for.

Right, let’s talk about mv. It stands for “move,” but that’s a bit of a lie. It’s more of a “relocate and/or rename” command. It’s one of the simplest, most powerful tools in your box, and 99% of the time, it just works. That last 1% is where things get spicy, and where you’ll be glad you read this. Think of mv less like a forklift and more like a librarian updating a card catalog. You’re not physically picking up the bits of the file and carrying them to a new location (most of the time). You’re telling the filesystem, “Hey, take this entry for old_name.txt and change it to point to new_name.txt or put it in that other directory over there.” This is why moving a 100GB file within the same filesystem is instantaneous, while copying it takes forever. You’re just changing a pointer, not duplicating all the data.

Right, cp. It’s the command you’ll use more than you’ll ever admit, and the one that will cause you more silent, screaming panic than any other when you get it wrong. It looks simple: cp [source] [destination]. And for a single file, it is. But the moment you need to copy a directory, you hit the first of many walls. Let’s get past them. The Non-Negotiable -r (or -R) Try to copy a directory without any flags. Go on, I’ll wait.

Right, let’s talk about making directories. It’s one of those things you do so often you stop thinking about it, which is exactly when you’ll make a spectacularly silly mistake. I’ve seen a senior engineer accidentally run mkdir node_modules in his home directory. Don’t be that person. Let’s get this right. The command is mkdir, short for “make directory.” At its simplest, you just give it a name and it obliges.

Right, touch. The name is a bit of a misnomer. You’re not gently caressing a file into existence; you’re either giving the filesystem a poke to update a timestamp or, if the file’s not there, conjuring it out of the digital void with the absolute bare minimum of content: zero bytes. It’s the command-line equivalent of saying, “I claim this land… for a future project, maybe.” Its primary, historical job isn’t even creation—it’s timestamp updating. Back in the day, build systems would use timestamps to figure out what needed recompiling. touch was the tool to trick them into thinking a file had just been modified so the build would proceed. The fact that it creates a file if one doesn’t exist is just a useful side effect.