Oh, and if your that paranoid about using a command with the potential to "nuke" something, then that's *double* the reason why you should have gone back and double checked it's usage. So you have no excuse what so ever. Sorry, but you just don't.
Just to expand on this, there is a lot of inconsistences with the command line. You have GNU where flags can appear in any order where as POSIX does not:
# correct in GNU, fails in POSIX:
ls /path -lt
You have common flags that change case in different tools (eg the recursive flag and port number flags are big ones that sometimes catch me out).
ssh -p port user@server
scp -P port user@server:/path destination
Then you have tools which don't even follow the usual rules for flags. eg utilities which have a single hyphen for words (i can't remember any examples for this off hand, but you do occasionally see it) or utilities which don't have hyphens at all
This is why if you're in any doubt about a commands usage and there's the potential to take your system offline, then you spend more than a 10 second glance at the man page. Heck, there's some commands I know from memory that I treble check before running (eg dd; i read my dd commands allowed 3 times before hitting [enter] as there's a high potential to mix up if= and of=).
The Linux/UNIX command line is a powerful tool, but there's a high potential for screw ups, so if in doubt, have a double check. And sometimes if you're sure, double check anyway. Otherwise laziness and inexperience will lead to you breaking things.Edited by Plan9 - 1/13/14 at 1:39am