If you’ve just logged into a Linux server and the terminal feels like an alien world, you’re not alone.

This hits a lot of WordPress owners, small-business devs, and new sysadmins: you connect via SSH, see a blinking cursor, and suddenly you’re scared to type anything in case you break the server.

Let’s fix that.

In this guide we’ll walk through the core skills: seeing where you are, moving around, and understanding the filesystem layout. All using simple commands you can run as a regular (non-root) user.

---

1. Before You Start: What You Need Ready

You don’t need to be a Linux pro to follow this. You just need:

• A Linux server you can connect to
• SSH access to that server
• A regular (non-root) user you can log in as

The original material assumes:

• You already know how to connect to your server using SSH
• You have a basic idea of what a terminal is and what a command looks like
• You’re using a normal user account, not root

So for this article, I’ll assume the same.

If you’re not sure whether you’re using root or not: if your prompt ends with # you’re probably root; if it ends with $ you’re normally a non-root user.

Safety tip: For normal file navigation and learning commands, stay on a regular user account. It lowers the risk of breaking something important.

Once you’re SSH’d in and you see your prompt, you’re ready.

---

2. Step One: Find Out Where You Are With pwd

When you first log in, Linux usually drops you into your home directory. That’s your personal playground on the server.

To check exactly where you are, run:

pwd

You’ll see something like:

/home/sammy

Quick breakdown:

• / is the top-level directory, called the root of the filesystem
• /home is a directory under / where user home directories live
• /home/sammy is the home directory for the user sammy

So your path is like a folder path on Windows, but with / instead of backslashes.

Why pwd matters: whenever you feel lost, pwd tells you “You are here”. Get used to using it often while you’re learning.

---

3. Understand the Filesystem from Your Home Directory

Your home directory is where you have “full dominion” as a regular user. In plain terms:

• You can create files
• You can create subdirectories
• You can usually edit and delete what you create there

The filesystem is a hierarchy starting from / (root) at the top. Under that, you get directories like:

• /home – where user home directories live

Your home directory is one step under /home, and that’s where you land when you log in.

That means when pwd shows:

/home/sammy

You can read it like:

• Root: /
• Inside root: home/
• Inside /home: sammy/

So the absolute path to where you are is /home/sammy.

This is enough to start building a mental map. As you navigate around, keep thinking: “Where am I relative to /?”

---

4. Move Around: Combine pwd With Basic Navigation

The source material focuses first on two ideas:

• Knowing where you are
• Getting an idea of what’s around you

We already covered the first one with pwd. The second one is about exploring.

Even without every command listed, you can follow this pattern safely as a normal user:

1. Check where you are

bash
pwd

1. Think about the structure

If you see /home/sammy, you know:
– Top is /
– Then home
– Then your directory sammy

1. Remember your home is your safe zone

Your home directory is the place where you should do your experiments:
– Create test files
– Create test directories
– Practice commands

Since we’re sticking strictly to what’s in the source, we won’t invent extra commands here. The key skill they highlight at this stage is:

• Use pwd to see your current directory
• Understand that this directory lives under /home, under /

That might sound basic, but when you get to real-world tasks like deploying WordPress or editing config files, this sense of “where am I in the tree?” is what prevents you from editing the wrong thing.

---

5. Think Safely: Users, Permissions, and “Dominion”

The source mentions you can do all this with a regular, non-root user. That’s on purpose, and it matters for safety.

Here’s the simple model to keep in your head:

• Root user: can do anything anywhere (including horrible mistakes)
• Regular user: has “full dominion” only inside their home directory

So when you log in as your normal user and you’re in /home/sammy:

• You’re supposed to be able to create and manage your stuff there
• You’re not supposed to mess with system-level directories higher up unless you really know why

For learning navigation and basic file operations, stay in your home directory:

• If something goes wrong, you’re only breaking your own files
• You’re much less likely to affect the whole server

This is the same logic I use teaching my kids not to test their new hammer on car windows.

---

6. Putting It Together: A Simple Navigation Routine

Let’s build a tiny routine you can use every time you log into a server. It uses nothing beyond what’s in the source plus common-sense safety.

1. Log in via SSH as your regular user.
   You’ll land in your home directory.

2. Confirm where you are.

bash
pwd

You should see something like /home/yourusername.

1. Remember the hierarchy.
   Mentally map it as:
2. / (root of everything)
3. /home (for users)

4. /home/yourusername (your personal space)

5. Do your experiments here.
   When you start learning file creation, editing, and manipulation, do it under your home directory.

This is a boring-sounding habit, but it’s what keeps production servers healthy.

---

7. Next Step: Keep Practicing in Your Home Directory

From the source, the goals at this stage are modest but important:

• Use pwd to know exactly where you are
• Understand that your home directory is under /home, under /
• Know that this home directory is where you have full control as a normal user

Once this mental model is solid, everything else in Linux navigation makes more sense: deeper paths, application directories, and eventually your WordPress or app files.

If this saved you time, bookmark CrushEdge for more fixes.