Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What things should any self-professed UNIX expert have under their belt? I'm looking to fill any gaps in my knowledge.

Some things I can think of off the bat:

  • Shell (interactive and scripting)
  • Common utilities (grep, ls, etc.)
  • vi (possibly Emacs too)
  • Some mix of sed / awk / Perl (preferably all)
  • Knowledge of networking standards
  • Ability to set up common programs: A mail server, file server and so on

Probably forgetting a lot, obvious and not-so-obvious. What else?

share|improve this question

closed as not constructive by txwikinger, Michael Mrozek, Shawn Chin, Eimantas, tsvallender Aug 11 '10 at 15:06

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

Should be a community wiki – txwikinger Aug 11 '10 at 13:30
levenez.com/unix/guru.html – ninjalj Mar 19 '11 at 22:33

As a UNIX expert, you should, at a minimum, be able to:

  • Build your system from source
  • Apply source patches to your system
  • Troubleshoot any problem you encounter
  • Understand what obscure knobs in your kernel do, and why you should probably not touch them
  • Administer your system
  • Protect your system
  • Maintain your system
  • Connect your system to other systems
share|improve this answer

From Development point of view :

  1. You should know how to use vim with cscope and ctags, this will help you to understand other peoples code faster. We learn alot from others code as well.
  2. Source control tools like CVS , svn etc.
  3. Debuggers e.g. gdb ,dbx
share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.