For CompTIA A+ Core 2 (220-1202), Domain 1, Objective 1.9, you need practical Linux file management skills on a client or desktop system. That means knowing where you are, what's in a folder, and how to handle files without causing downtime. In this post, you'll learn the everyday commands used for support work: ls, pwd, mv, cp, rm, chmod, chown, grep, and find.
These commands feel simple, yet small mistakes can create big problems. Linux is also case-sensitive, so Report.txt and report.txt are different files. Practice in a safe place first, such as a test folder in your home directory. Be extra careful with rm, chmod, and chown, because the wrong target can remove files or lock users out.
Understand where you are and what's in the folder
Linux file management starts with a mental model. Linux uses a single directory tree that begins at / (the root). Every file and folder sits somewhere under that tree, even external drives when they are mounted.
Paths come in two forms. An absolute path starts from /, such as /home/alex/Downloads. A relative path starts from your current location, such as Downloads or ../Documents. Because of that, the same command can succeed or fail based only on where you run it.
On a desktop support ticket, this detail matters. A user might say, "I copied it," yet they copied to a different folder. Another common issue happens when a script runs from a scheduled task. It may have a different working directory than a terminal session. If you build the habit of checking location and listing contents first, you avoid guesswork and reduce errors.
Use pwd to confirm your current location
Your current working directory is the folder the shell treats as "here." Relative paths rely on it. When you run cp notes.txt Backup/, the shell looks for notes.txt in the current directory, not across the whole system.
The pwd command prints the full path of your current location. On many Linux desktop systems, you'll often see a home directory like /home/user or /home/jordan. That output tells you, at a glance, whether you are working in the right place.
Picture a simple mistake: you meant to delete a test file in ~/Downloads, but you opened the terminal in ~/Documents. Running pwd takes one second and can prevent hours of recovery work.
Use ls to list files, spot hidden items, and read details
After you confirm your location, ls helps you inspect what's there. Running ls shows file and folder names in the current directory. For troubleshooting, you often need more detail, so a few options matter for Core 2 questions and daily support work:
ls -l: Shows a long listing, including permissions, owner, group, size, and timestamp.ls -a: Shows hidden items too, including names that start with a dot.ls -lh: Combines long listing with human-readable sizes (KB, MB, GB).
Hidden dotfiles (like .bashrc or .config/) store user settings on Linux desktops. If a browser profile, shell setting, or app preference looks "missing," it may sit in a dot directory. Seeing those files can turn a vague complaint into a clear next step.
You may also see options like ls -t to sort by time, which can help when you're looking for the newest download. Still, exam questions tend to focus on -l, -a, and -h, because they connect directly to permissions, ownership, and file visibility.
Copy, move, and remove files without breaking your system
File operations on Linux are powerful because they are direct. That speed is helpful during support work, yet it also means you should slow down before pressing Enter. A careful workflow reduces mistakes when you're organizing user data, cleaning up temporary files, or preparing a profile migration.
Three habits are worth adopting early:
- Use Tab completion to reduce typing errors.
- Put quotes around names with spaces, like
"Final Report.docx". - Re-check the source and destination paths before you run the command.
Those habits matter most when you work outside your home folder, or when you use wildcards.
Copy with cp, including folders and safer overwrites
The basic pattern is cp source destination. If the destination is a directory, cp places the copy inside it. For example, copying a file into Documents is a common desktop task when cleaning up a crowded Downloads folder.
When you need to copy a directory, use recursive mode: cp -r FolderName DestinationFolder. Without -r, cp won't copy directory contents.
Accidental overwrites are another common support issue. Add -i for interactive prompts: cp -i source destination. That prompt forces you to confirm before replacing an existing file. It's a simple guardrail when you're copying configuration files or templates.
For advanced cases, cp -p preserves timestamps and some attributes. You don't need it for every task, but it can matter when you want to keep "last modified" times during a migration.
Move or rename with mv, and understand what changes
The mv command does two jobs: it moves files and it renames them. Renaming is just moving within the same directory.