The File Operations Every DevOps Engineer Must Master
The Backup-Before-Edit Habit
The single most important habit in production operations is creating a backup before editing any configuration file. The command cp config.conf config.conf.bak takes less than a second but can save hours of downtime. Senior engineers do this reflexively — it's as automatic as breathing.
Some teams take this further with timestamped backups:cp nginx.conf nginx.conf.$(date +%Y%m%d-%H%M%S). This creates a named snapshot you can reference during post-mortems. Combined with diff, you can see exactly what changed between versions.
Safe File Operations
Best practices for manipulating files safely on production servers.
cp -p— Preserve permissions when backing up.mv -i— Ask before overwriting files.rm -i— Confirm each deletion interactively.- Always
pwd+lsbeforerm -rf.
Content Inspection
Tools for quickly reading and monitoring file content.
cat— Quick view for short files (<100 lines).tail -n 20— Last 20 lines of any file.tail -f— Stream logs in real-time.head -n 10— Check file headers quickly.
The rm -rf Safety Checklist
The rm -rf command is the most dangerous tool in a Linux administrator's toolkit. There is no "undo" — deleted files are gone forever. Before every rm -rf, senior engineers follow this mental checklist:
- Run
pwd— verify you're in the right directory. - Run
ls target/— verify the target contents. - Double-check the path — no typos, no trailing spaces.
- Consider
rm -rifor interactive confirmation first. - Execute the command only when 100% confident.
