Following sti's shell history meme, here are
some meaningless shell history statistics from my home computers. (By the
way - I would've done that one-liner like this: history | awk '{print
$2}' | sort |uniq -c | sort -rn|head - two more pipelines out of
habit.)
My home Mac:
$ history|awk '{a[$2]++ } END{for(i in a){print a[i] " " i}}'|sort -rn|head
127 ssh
52 ls
45 ping
32 cd
26 sudo
13 open
12 mount
10 top
10 cat
9 df
Surprise: mount - turns out I often use mount without
parameters to see which device a newly attached hard disk appears at.
My Linux gateway box
$ history|awk '{a[$2]++ } END{for(i in a){print a[i] " " i}}'|sort -rn|head
47 ls
40 cd
39 screen
38 sudo
24 ps
20 w
19 ping
17 mount
15 cat
14 tuxgdg
No surprises, really - I mostly use this box for IRC in a screen session - but lately also for playing with my Tux Droid, hence tuxgdg.
My work laptop (Linux)
$ history|awk '{a[$2]++ } END{for(i in a){print a[i] " " i}}'|sort -rn|head
92 sudo
76 ssh
41 echo
38 ping
31 ipsec
22 tail
22 cd
21 ls
16 cat
14 vi
This computer is mostly used for remotely connecting to the work VPN (hence ipsec), and through that connecting to work servers using SSH, and the rest is done through Gnome or a web browser.
ping appears everywhere, most likely because my ISP is
quite unstable at times. Also, I'm more vi than I thought.
Again I'm staying a bit too late at the office, compensating
for some overly late "mornings" as well as doing some
experimental work that's not scheduled for during my normal
working hours. I brushed off my mad DHTML skills and made
some fancy dynamic web page stuff for our internal test
systems, just to
realize as I was nearing completion, that the snazzy new
features didn't work at all in Internet Explorer. Luckily,
Internet Explorer is not widely used here, but it is a sort
of annoying feeling. I was all happy-happy-joy-joy when I
tried to use document.all in Javascript (it was
many years since I made any serious Javascript effort), and
Firefox politely informed that the W3C-conformant way of
doing what I was trying to do, was to call the
document.getElementById() function. So I was lured
into the delusion that I was actually doing some bad-ass
cross-browser stuff. But of course I wasn't. Humbled, I went
back to replacing myself with little shell scripts here and
there. 