(Useful) Stupid Unix Tricks?

So the other day I messaged another admin from the console using the regular old 'write' command (as I've been doing for over 10 years). To my surprise he didn't know how to respond back to me (he had to call me on the phone) and had never even known you could do that. That got me thinking that there's probably lots of things like that, and likely things I've never heard of. What sorts of things do you take for granted as a natural part of Unix that other people are surprised at?

Comments

session-sharing with screen -x

[FooAtWFU]

(used in my company for doing the agile/extreme "pair programming" think with a remote devloper, among other things).

screen is awesome.

grep and awk

[yakmans_dad]

So much easier for me to use than perl. I presume the modern unix user prefers perl.

I never knew that command

[PingXao]

And I've been administering Linux systems for awhile now. Step back for a moment and you'll find that "man pages" and "info" are actually a pretty awful way to distribute documentation. As a supplement they'd be fine, but as the main source of information on how to use many commands... not so much.

Re:I never knew that command

[PhilipPeake]

This is only true because people write such terrible and incomplete manual pages.

The original Bell Labs man pages completely described the system from the point of view of an administrator or user. The only better documentation was the source.

The current blight of wimpy, inaccurate and incomplete man pages seems to originate from the GNU developers who insist on using the terrible "info" crap, writing huge volumes of text with no real content, and the tradition is continued by Linux developers who generally provide little or no man page documentation -- presumably in the hope that users of their software will be tempted to ask questions on various mailing lists where they can be ritually disemboweled for displaying such a lack of understanding and disturbing the peace of the cognoscenti who have much more important things to do than answer questions of mere users of their software.

Re:X-forwarding

[BigJClark]

... or even funnier, is how long (as in decades) we've been able to do that.

Bah, subtlety:

[FooAtWFU]

:(){ :|:& };:

Re:rm -rf /

[acidreverb]

Mediocre minds think alike. Great minds are unique.

Re:Tab

[jcam2]

You'd be surprised how often I have seen experienced programmers manually type out long commands or directory paths, instead of using tab completion. Sometimes I have to restrain myself from ripping the keyboard from their hands and using tab to enter the path myself in a 10th of the time.

Re:rm -rf /

[Omega996]

sudo is for ubuntu wannabes - real UNIX admins don't sudo - they su - .

Re:rm -rf /

[j79zlr]

Fortunately, I didn't permanently lose anything between good backups and Norton Disk Doctor.

Yes, you do need good backups whenever you are running Norton products. Good idea.

Re:rm -rf /

[Teilo]

No. People who run as root all the time are either n00bs or morons.

N00bs if they have never spoken the words, "Oh sh*t!" after running a command;

Morons if they have.

Re:rm -rf /

[Omega996]

if you haven't said "oh shit" while doing something as root, you haven't done UNIX administration in a busy production environment.

Re:Useful tricks.

[cowens]

Next trick, back ticks. `` Back ticks substitute the output of a command within a command.
Ex. Name a file after the date. echo "hi" > `date +%Y%M%d`.txt

Don't use backticks unless you are stuck with bourne shell. Use $() instead:

echo hi > $(date +%Y%M%d).txt

They have two benefits over backticks: you can nest them and they are easier to see.