TL;DR – Linux file management
- Rename or move:
mvhandles both jobs, which is why so many people use it too casually. - Copy carefully:
cp -ris fine for one-off duplication, butrsyncis the better habit for repeatable copies. - Delete last:
rm -rshould be the final step in a reviewed workflow, not the first reflex. - Check intent first: Most command-line damage happens because the target path is wrong, not because the command syntax is wrong.
Start here: If you only need one exact task, jump straight to How to Rename a Directory in Linux or How to Copy a Directory in Linux. This page is the compact field guide that ties those jobs together.
| Topic | When | Command |
|---|---|---|
| Rename a folder | Same place, new name | mv old-name new-name |
| Copy a tree | One-off duplicate | cp -r src dst |
| Repeatable copy | Keep source and destination aligned | rsync -a src/ dst/ |
| Delete a directory | Only after review | rm -r old-dir |
Linux file operations look simple right up until you are working on production data, a mounted volume, or a path with spaces in it. Then the difference between rename, move, copy and delete stops being academic.
This guide is the page I wish more people had open before they start rearranging a server. It does not try to teach every file command on Linux. It focuses on the handful that matter most in everyday admin work, plus the mistakes that actually cause trouble.
The safe mental model
Think in outcomes, not commands. If the original data should continue to exist, you want a copy. If the data should stay the same but the name should change, you want a rename. If the data should live in a different location, you want a move. If the data should disappear, that is the point where deletion enters the conversation.
- Rename:
mv project-old project-archive - Move:
mv report.txt /srv/reports/ - Copy:
cp -r app app.bak - Delete:
rm -r old-release
The commands you will actually use
mv is powerful because it does more than one thing. That is also why it catches people out. If the target already exists and is a directory, your source may be moved inside it instead of renamed to it. That is not a Linux bug. It is Linux doing exactly what you asked.
cp -r is the blunt instrument. It is perfect when you just need another copy. rsync -a is the better long-term habit when you care about repeat runs, preserving attributes and seeing what is changing.
The mistakes that cause most pain
- Forgetting where you are: Run
pwdbefore destructive commands if you have changed directories a few times. - Assuming a target does not exist: Use
ls -ld target-namefirst when a rename absolutely must not become a move. - Ignoring spaces: Quote paths like
"My Folder"or escape spaces properly. - Mixing slash semantics: With
rsync, a trailing slash changes whether you copy the directory itself or its contents.
A workflow that stays safe under pressure
When the change matters, I do the same small routine every time. Confirm the current working directory. List the parent directory. Take a backup or at least prove that I could recreate the data if needed. Then run the command. Then list the result immediately.
That sounds slow until you compare it with restoring a deleted directory, cleaning up a mistaken move, or explaining why the backup you thought you made was just a rename.
If you want the deeper one-task versions of this page, read How to Rename a Directory in Linux, How to Copy a Directory in Linux, and How to Delete Files in Linux with rm, shred and find. If you are building out a fresh server workflow, the broader setup sequence is Ubuntu Server First 30 Minutes