Dr. Johns discusses 5 common Linux commands everybody gets wrong. This is the next video in our series. 1st Video: …
[ad_2]
source
Dr. Johns discusses 5 common Linux commands everybody gets wrong. This is the next video in our series. 1st Video: …
[ad_2]
source
Lorem ipsum dolor sit amet, consectetur.
5 Linux commands noobs* get wrong ftfy
This is really helpful. What I do not understand is ps aux command. The most commands have switch like –. I wonder why not ps –aux?
Thanks for very helpful tips
At least in bash and similar shells, your find command will not work properly. bash will expand glob characters in double quotes, it will not expand glob characters in single quotes. So you if you use glob characters in your pattern, you must use single quotes around them (or precede stars with backslashes).
I do welcome the "rsync src/ dst" syntax and find it very useful, as it is on par with how "cp" works, and especially because in bash, it's typically nontrivial how to select all files, including hidden ones.
Good to know
It'd be lovely if you would've shown examples right in the terminal rather than just explaining with words
nice explanation and thanks for info… One critic, please make your commands bit larger and middle of the screen so low resolution windows can see. keep up the good work.. <3
the number of (recursive) directory copies I got wrong with rsync! I think I've figured it out now, but am never quite sure.
I started with Linux back in 1996 and UNIX sysadmin stuff about 8 years before that and I can't fault the 5 mistakes you've picked up, I've done them all in the past – and still have to really think about parameters to rsync and forward slashes.
For the find command, you can use quotes but you can do it in one character by escaping the wild card – "find . -name *.txt also works fine.
If I am teaching Linux to others, I try to get them to understand "escaping" first before moving on to quotes, because you will also be aware that there are times you use single quotes that work differently to use double quotes – and then, of course, there's the back quotes as a method to grab the output of a command, rather than running the command itself.
But a very good and helpful video.