(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?

rm -rf /

[by Anonymous Coward]

rm -rf /

Bah, subtlety:

[FooAtWFU (699187)]

:(){ :|:& };:

Re:Bah, subtlety:

[jkiol (1050424)]

@$**& well we know it works in cygwin too.

Re:rm -rf /

[acidreverb (1339035)]

Mediocre minds think alike. Great minds are unique.

Re:rm -rf /

[by Anonymous Coward]

OMG OMG What did I do. What did I do. I am so fired. I am so EFFIN fired.

Re:rm -rf /

[butalearner (1235200)]

I got something similar to these from some website that I have long forgotten: alias AvadaKedavra kill -9 alias Obliviate rm -rf alias Alohomora chmod -Rf ug+w alias Accio grep -Ir \!:1

Re:rm -rf /

[Frymaster (171343)]

or the "unix koan" grep "" /dev/null

Re:Show attached block devices

[duguk (589689)]

Some more common ones I've thought of:

screen - too useful, run apps in a virtual console which you can attach, deattach and share

cd `pwd -P` - Jump into the real directory (from a linked directory).

history - use it with grep if you forgot what you did

strings - just show the printable strings from a file

tail and head - tail -f is a lifesaver

sftp - i really shouldn't need to explain this.

file - do magic stuff

Hope that's some help.

Re:Show attached block devices

[MrMunkey (1039894)]

cd -

Change to your previous directory. It's great for going from dev to test environments from time to time.

Re:Show attached block devices

[aniefer (910494)]

ctrl+r (in bash?): reverse incremental search through history.
pushd/popd , change directory saving the old one on a stack.

Re:Show attached block devices

[HTH NE1 (675604)]

This shows all attached block devices (it also errors like crazy, hence the | more)

blockdev --report /dev/* | more

Redirect stderr much?

blockdev --report /dev/* 2> /dev/null

Re:rm -rf /

[orclevegam (940336)]

rm -rf /

wtf??? (do not try this at home)

Really? What does it do? Think I'll try it and s
CARRIER LOST

Re:rm -rf /

[macshome (818789)]

Pshaw! All 1337 sysadmins just live as root!

Re:rm -rf /

[mr_mischief (456295)]

cat /dev/urandom > /dev/dsp

Re:rm -rf /

[by Anonymous Coward]

sleep 8h; cat /dev/urandom > /dev/dsp

That's my alarm clock.

Well

[by Anonymous Coward]

Well.

dd if=/dev/zero of=/dev/sda1

Re:Well

[FooAtWFU (699187)]

Not quite the same, but in a similar vein, cat /dev/urandom > /dev/dsp

Sometimes a quick white-noise machine is relaxing. Heck, I used that command in combination with 'at' to act as a makeshift alarm clock when I was just moving into my first apartment and had forgotten my only other electronic device with an alarm (my cell phone) at the office.

session-sharing with screen -x

[FooAtWFU (699187)]

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

screen is awesome.

There is this part ...

[140Mandak262Jamuna (970587)]

... Generally people are surprised by the fact that you could type some strange incantations into a black window like awk grep etc and make the computer do things without touching the mouse. Yeah, some are surprised by that thing.

Re:There is this part ...

[Forty Two Tenfold (1134125)]

I once made my friends' jaws hit the floor when I burned a cd for them - from console.

And once I had this strange feeling that something was wrong with the CD drive of a machine I was working at in the console until I realized I was opening and closing the CD tray on a machine in another room!

Re:There is this part ...

[infinite9 (319274)]

I do both microsoft and unix development. This has led to some interesting situations. I wrote a mathematical parser in c#/.net that could process math expressions at runtime using Regex to get tokens from the expression. The regex wasn't too bad. But after a code review, my pointy-haired manager made me comment each symbol in the regex. 40 lines of comments to describe 1 line of code.

As a consultant, VI is my absolute favorite tool. Not on unix projects, on microsoft projects. It always happens eventually. Someone needs to modify a file in a way that screams for regex search with replace, but is a nightmare in visual studio or some other windowy editor. So I have them stand behind me while I write an long, arcane-looking regex line in VI. When I press enter, the entire file instantly morphs into exactly what they want. I can think of no better way to justify my exorbitant bill rate. lol

Tab

[computersnstuff (799942)]

I'm sure everyone at some point is surprised of tabbed completion.

Re:Tab

[by Anonymous Coward]

I'm sure everyone at some point is surprised of tabbed completion.

Woah! Got any more?



(yes, I'm being sarcastic)

Re:Tab

[jcam2 (248062)]

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:Tab

[Craig Davison (37723)]

With bash, you can even get tab completion for hostnames. Try this:

ssh user@l[tab]

Everything after the @ is filled in from /etc/hosts.

Re:Tab

[gEvil (beta) (945888)]

I just tried using this in Word. Instead of finishing the word I was typing, it kept on moving the little "insertion line" thing to the right. I already filed a bug report, but do any of you have a quick fix?

I never knew that command

[PingXao (153057)]

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 (711883)]

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.

X-forwarding

[mikeb (6025)]

I've seen Windows people go slack-jawed in astonishment as I ssh to the other side of the world and run X programs over forwarding.

Some refuse to believe it, others shake their heads and walk away.

Re:X-forwarding

[BigJClark (1226554)]

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

Re:X-forwarding

[Chris Pimlott (16212)]

You could easily have an entire Ask Slashdot just on ssh, perhaps the greatest unix command ever invented.

One of it's many great uses is creating secure tunnels:

ssh user@remotehost -L123:example.com:456

Open a tunnel on your local machine, port 123, to example.com, port 456, via the remote host

ssh -R lets you go in the opposite direction (tunnel from remote end to local end), but if your application supports SOCKS, it's even easier:

ssh user@remotehost -D8080

Creates a secure tunnel supporting the SOCKS protocol.

Talk / DD / Mount

[p14-lda (517504)]

People seem to be losing the ability to use all the older manual ways of doing things.

On the older systems, talk was a great utility.

dd, device duplicator / disk destroyer

mount, what I can't have a desktop icon?

also managing disk volumes and the old conventions of /opt, /u, /usr, /usr/local

This new fangled Linux craze with all of the UI tools is feeding it. Redhat is training admins that are dependent on a given release of their enterprise software (which I am a huge fan of) but not teaching them how it works under the hood.

How about slirp? scp?

The one ray of hope seems to be a new generation hacking their bsd and linux based (iPhone/Android) phones and having fun in a somewhat embedded (but full blown) *nix environment.

cd -

[JustinOpinion (1246824)]

In terms of navigation directories efficiently, I find that "cd -" is often forgotten (changes directory to your previous directory). I personally find it very useful, and couldn't live without it!

One word:

[MMC Monster (602931)]

Showers

Job control.

[Craig Davison (37723)]

fg, bg, kill, Ctrl-Z, &. Learn it. Know it. Live it.

Even if they do know about job control, I've seen people look for a background job with ps, and then kill it using the PID. In most shells you can just do kill %, e.g. kill %1

short list of shell tips

[James Youngman (3732)]

Assuming you already know the simple stuff like how to use shell quotes correctly, what you can do with ps and top, ...

1. Using awk '$3 ~ /foo/ { bar }' to grep just one column of a file
2. reset
3. find . -blah -exec quux \+
4. Adding : to the front of complex commands you just typed but realise you don't want to execute yet so that they get into your shell history
5. Meta-T in Bash for swapping arguments
6. find . -printf X | wc -c for counting files (since find |wc -l would miscount files with newlines in the name)
7. set, shift and implicit shell loops (for without in)
8. "${foo:-bar}" and similar
9. "${x%%.ext}.newext"
10. comm -3 <(sort long) <(sort short)
11. unalias rm

Share mouse and keyboard

[pieleric (917714)]

When I pop up with my laptop to discuss with a colleague, after a while I might do on their computer:
xhost +mylaptopname

and on my laptop I do:
x2x thecomputername:0 -west

Then suddenly my mouse can go over the two computers, my keyboard works on both as well, and I can even copy-paste between the two computers. It looks like the two computers got united. In a flash, newbies get a new idea of what means unix and X ;-)

My personal fave

[44BSD (701309)]

echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc

grep --color

[krappie (172561)]

grep --color

For some reason, many people are greatly surprised when they figure out that grep will highlight matches for them.

lsof

[pak9rabid (1011935)]

lsof is a LIFE SAVER for trying to find what's still using something in a mounted resource when trying to unmount something. For example:

lsof /mnt/myMount

That will list which processes have anything under /mnt/myMount open

It's also useful to find who's accessing what device. For example, say you're trying to listen to an mp3 and Amarok bitches about the sound device not being available. In that case, you could do something like this (assuming you're using ALSA):

lsof /dev/snd

That will list what processes are accessing any of your ALSA sound devices.

Re:rev

[genner (694963)]

The rev command has got to be one of the most useless Unix commands I've ever come across. It's almost as if someone's first c program somehow got taken up as a part of standard Unix! Maybe in the days before sed and awk and perl it had some function in pipes that I can't grok, but nowadays other than making hints for video game websites I can't imagine what it's for.

Unhackable encryption of course.

Re:rev

[Chris Pimlott (16212)]

I sometimes use rev to sort text by the end of the line, not the first. This is often useful when comparing two similar file structures.

For example:

$ wc -l foo/* bar/*
      6 foo/dead.letter
    86 foo/xorg.conf
      6 bar/dead.letter
    54 bar/xorg.conf

$ wc -l foo/* bar/* | rev | sort | rev
    86 foo/xorg.conf
    54 bar/xorg.conf
  152 total
      6 foo/dead.letter
      6 bar/dead.letter

(Yes, I'm aware you can use sort -k to specify the sort key, but this is quicker and easier)

Re:Listing directory contents without the ls comma

[marcansoft (727665)]

You're not giving echo an asterisk as a paratemer. You're giving the shell an asterisk, which it dutifully expands. echo (which in this case is a shell builtin, but it doesn't have to be then just echoes them back.

This isn't some echo peculiarity. It works for anything, even commands that don't normally take files, or even with files that look like switches (conversely, if you want to treat all subsequent arguments as files, not switches, most programs have a '--' switch):

$ ls
a -l b c
$ ls *
-rw-r--r-- 1 marcansoft users 0 2008-11-05 21:58 a
-rw-r--r-- 1 marcansoft users 0 2008-11-05 21:58 b
-rw-r--r-- 1 marcansoft users 0 2008-11-05 21:58 c
$ ls -- *
a -l b c

In the second example, ls sees "ls a -l b c" and takes -l as a switch instead of a filename.

Re:Listing directory contents without the ls comma

[elgatozorbas (783538)]

Maybe an ex-windows user who assumed "delete /bin" was the linux equivalent of "empty wastebasket" ?

Re:This one always surprises people for some reaso

[interiot (50685)]

• Optimized version of that: find / | grep -i $SOMETHING
• Even more optimized: find / -iname $SOMETHING
• However, most systems support locate/updatedb already, and that's much faster.

Re:grep -R

[multipart/mixed (163409)]

Hell, I think it's probably a GNU extension, because it's still not in Solaris.

I think rgrep appeared around BSD 4.4, though.

Oh well. I still surprise people with backticks. *sigh*

-exec as a test

[Chris Pimlott (16212)]

One great feature of find that many people are unaware of is that you can use -exec as a test, not just as an action. For example, this is equivalent to your command above:

find . -exec grep -q {} \; -print

The "-print" action is only executed if the -exec command returns success.

You can do a lot of handy things with this. Here's a real-world example from earlier today. I wanted to change the mime-type of all the xml files in my svn repository from "application/xml" to "text/xml":

find . -name \*.xml -exec sh -c "svn propget svn:mime-type {} | grep -q application/xml" \; -exec svn propset svn:mime-type text/xml {} \;

Re:Find / Grep

[by Anonymous Coward]

I have a theory that find + xargs + grep is Turing-complete. Can't prove it, but it feels right.

Re:A simple search

[AKAImBatman (238306)]

Xargs is much more fun with complex data processing. e.g.

Convert all PSDs to PNGs:

ls *.psd | cut -d . -f 1 | xargs -L1 -i convert {}.psd {}.png

Parse out and sort column 2 from a semicolon delimited file:

cat myfile.txt | cut -d \; -f 2 | sort > output.txt

Oh, I almost forgot about one of my favorite tricks. Count the number of items:

wc -l
(paste the list into the window and then type CTRL-D)

It even works when the list of items has oddities. e.g. I had a list where every other line was blank. So I needed to count n/2 the value. Except that one of the blank lines wouldn't copy, so I actually needed (n+1)/2.

echo $(($((`wc -l`+1))/2))

Want to make sure your sig is under 120 characters? Type "wc -c" in, paste it into your terminal, then press CTRL-D. Instant character count.

Ah, all the fun stuff you can do with Unix tools.

Re:A real time saver!

[Mish (50810)]

DISCLAIMER: Don't run this!
I didn't think I needed to say this, but I just showed someone this and they thought it was a legitemately helpful command...