5 ms·
> In general I found these 14 commands end up being the smallest number anyone really needs to do basic CLI work.. What should an advanced user know? Everythin
by jaseemabid 13y ago
> In general I found these 14 commands end up being the smallest number anyone really needs to do basic CLI work..
What should an advanced user know? Everything provided by coreutils, stuff that goes in /bin etc? Also sed, awk and common tools for simple text processing?
- e12e 13y agoI think there are several valid definitions for "advanced" in this context. While basic awk/sed knowledge is certainly useful -- if you can do the same thing in python/ruby/perl that might be fine. Knowing a little bit about writing valid ksh/bash shell scripts (being at least aware of bash-isms) would certainly be useful for sys adm work. My opinion is that the full gnu (and/or bsd) userland has grown so large over the years, that saying that you should know it all is probably overkill -- but knowing how to look things up (man, info) is a must. As Zed's implied -- GNU documentation could stand to be improved vs bsd man pages -- although the info manuals can be quite useful.
- zedshaw 13y agoAfter these commands I don't think learning a ton of more commands makes you better at working a computer. After this, sitting down to actually setup a working Unix box and then hardening it will teach you a crazy number of commands and things. More importantly it'll teach what all those little processes and services do on the computer. However, I will say that learning how to effectively use grep and sed are probably the only big omissions from my list. But, those are outside the scope of this little book given those commands have whole books devoted to them.
- jaseemabid 13y agoWell said! Its probably the tinkering that eventually teach people that something that is in coreutils is worth looking into.