Command-Line Navigation and File-System Management

Why the Command Line Matters in a Data Center

Data center servers almost never have a graphical desktop. You manage them through a text-based interface called the command-line interface (CLI). Speed, precision, and the ability to automate tasks through scripts make the CLI the standard tool for data center technicians. CompTIA A+ Core 2 and CompTIA Server+ both test Linux command knowledge, and the CNet CDCTP program expects you to work confidently in a Linux terminal from day one.

The Linux Filesystem Hierarchy Standard (FHS)

Linux organizes all files in a single tree that starts at the root directory, written as `/`. Every drive, partition, and network share is attached (mounted) somewhere inside that tree. The Filesystem Hierarchy Standard (FHS) defines where specific types of files live:

| Directory | Purpose |

|-----------|--------|

| `/bin` | Essential user command binaries (ls, cp, mv) |

| `/etc` | System-wide configuration files |

| `/home` | Personal directories for regular users |

| `/var` | Variable data: logs, mail, print spools |

| `/tmp` | Temporary files; often cleared on reboot |

| `/proc` | Virtual filesystem exposing kernel and process info |

| `/usr` | Secondary hierarchy: programs, libraries, documentation |

Knowing FHS lets you find log files quickly (`/var/log`), locate configuration files (`/etc`), and avoid touching directories that the OS relies on.

The Ten Core Navigation and File-Management Commands

1. `pwd` — Print Working Directory

Shows your current location in the filesystem tree. Always run `pwd` first when you open a new terminal session to confirm where you are.

2. `ls` — List Directory Contents

`ls -l` gives a long listing with permissions, owner, size, and modification date. `ls -la` also shows hidden files (names beginning with `.`).

3. `cd` — Change Directory

Move through the tree: `cd /var/log` goes to an absolute path; `cd ..` moves up one level; `cd ~` returns to your home directory.

4. `mkdir` — Make Directory

`mkdir reports` creates a subdirectory in the current location. `mkdir -p archive/2024/q1` creates nested directories in one step.

5. `touch` — Create an Empty File or Update Timestamps

`touch server_health.log` creates an empty file if it does not exist, or updates its timestamp if it does.

6. `cp` — Copy Files or Directories

`cp file.txt backup/file.txt` copies a file. Use `cp -r sourcedir/ destdir/` to copy a directory and all its contents recursively.

7. `mv` — Move or Rename

`mv oldname.log newname.log` renames a file in place. `mv file.log /var/log/app/` moves it to another directory. There is no undo for `mv` at the CLI, so verify the destination before pressing Enter.

8. `rm` — Remove Files or Directories

`rm file.log` deletes a file permanently. `rm -r directoryname/` removes a directory and all its contents. `rm -rf /` or any accidental recursive delete on a production path can destroy a live system — always double-check your path. Never run `rm -rf` as root unless you are absolutely certain of the target.

9. `find` — Search the Filesystem

`find /var/log -name "*.log" -mtime -7` finds all `.log` files in `/var/log` modified in the last seven days. `find` is essential for locating misplaced files during troubleshooting.

10. `tree` — Display Directory Tree

`tree /etc` prints a visual hierarchy. If `tree` is not installed, `tree` can be added with the system package manager. Use it to quickly understand an unfamiliar directory layout.

Absolute vs. Relative Paths

An absolute path starts from root: `/home/student/logs/app.log`. A relative path starts from your current directory: `logs/app.log` (if you are already in `/home/student`). Mixing these up is the most common source of copy or move errors.

Safety Considerations at the CLI

• Work as a regular user, not root, during practice. Elevated privileges (root or `sudo`) are needed for system administration but dramatically increase the risk of accidental system damage.
• Verify your path with `pwd` before any destructive command (`rm`, `mv`, or `cp` that overwrites).
• Never run unfamiliar commands on a production server. Use the dedicated practice partition provided in lab.
• Physical safety: Lab servers are energized equipment. Follow your facility's policies — do not open server chassis without authorization, and apply lockout/tagout procedures if any physical hardware work is required. Wear anti-static protection when handling components.
• Data integrity: Before renaming or deleting log files in any real environment, confirm that no monitoring agent or application is actively writing to them.

Documenting Your Work

A professional technician records every command and its output. In this course you will use a lab log notebook for that purpose. Good documentation supports troubleshooting, compliance audits, and knowledge transfer to teammates — all expectations in a production data center.