Code:[andy@hp ~]$ history | awk '{print $2}' | awk 'BEGIN {FS="|"} {print $1}'|sort|uniq -c | sort -n | tail | sort -nr 78 fortune 65 sudo 61 ls 50 pacman 37 man 37 echo 21 rm 17 uname 15 clear 14 cd
-
-
Code:
[thomas@thomas-tablet ~]$ history | awk '{print $2}' | awk 'BEGIN {FS="|"} {print $1}'|sort|uniq -c | sort -n | tail | sort -nr 183 sudo 77 ls 67 nano 49 cd 35 make 33 g++ 28 gst 27 ruby 27 emacs 25 cat
-
ALLurGroceries Vegan Vermin Super Moderator
Hm sure why not.
Code:62 cd 56 ls 39 make 37 ssh 37 cp 31 time 30 sudo 19 ping 13 nano 12 kvm
-
This is a bit of an interesting thread
Code:311 ls 245 clear 121 cd 62 sudo 56 vim 55 cat 32 rm 31 clyde 30 libreoffice 22 unison
Thank god this isn't showing how frequently I compile latex documents inside vim! -
NO emacs, NO nano!
VI!
**starts a fire. -
Code:
psymin@psymin ~ $ history | awk '{print $2}' | awk 'BEGIN {FS="|"} {print $1}'|sort|uniq -c | sort -n | tail | sort -nr 115 cd 104 ls 55 eog 41 ./mcmap 16 java 16 ./pigmap 15 ./minecraft.sh 11 cp 10 ./c10t 8 su
Here is root's:
Code:psymin ~ # history | awk '{print $2}' | awk 'BEGIN {FS="|"} {print $1}'|sort|uniq -c | sort -n | tail | sort -nr 60 halt 42 exit 41 ifconfig 33 ls 29 dmesg 25 df 24 cd 18 fdisk 17 mount 15 umount
-
My #1 command is
Code:rm -rf . /*
-
ThinkRob: LOL! That's my favorite command to run when I finish testing a distro.
Note to beginners, DON'T run that! It will delete everything! -
Code:
renan@voyager:~$ history | awk '{print $2}' | awk 'BEGIN {FS="|"} {print $1}'|sort|uniq -c | sort -n | tail | sort -nr 131 sudo 84 ls 66 cd 51 dmesg 26 ps 17 free 15 vim 14 ./test_pyevolve.py 14 hg 14 apt-cache
-
Code:
knightzero@MENTALIST-NIX:~$ history | awk '{print $2}' | awk 'BEGIN {FS="|"} {print $1}'|sort|uniq -c | sort -n | tail | sort -nr 191 sudo 132 ssh 64 ping 39 exit 36 cd 26 synergyc 26 ls 24 vi 23 ps 17 nrclientcmd
Code:knightzero@BRAINWODE:~$ history | awk '{print $2}' | awk 'BEGIN {FS="|"} {print $1}'|sort|uniq -c | sort -n | tail | sort -nr 83 sudo 80 screen 63 exit 62 ssh 18 cd 17 irssi 16 ls 12 ping 9 vi 9 tt++
-
Code:
12 sudo 8 ssh 8 rsync 4 vim 4 ps 3 kill 3 history 2 ls 2 ifconfig 2 exit
Code:( ,&&&. ) .,.&& ( ( \=__/ ) ,'-'. ( ( ,, _.__|/ /| ) /\ -((------((_|___/ | ( // | (`' (( `'--| _ -.;_/ \\--._ \\ \-._/. (_;-// | \ \-'.\ <_,\_\`--'| ( `.__ _ ___,') <_,-'__,' `'(_ )_)(_)_)'
-
Code:
firefox 5 cd 5 umount 6 ping 6 uname 7 exit 10 ls 11 df 15 sensors 89 sudo
-
I assumed it was for fun, it can't be very accurate.
The filtering of the history file isn't very robust because it only crudely parses the commands entered - and it seems like it would be a very complex thing to do accurately. For example, one of the awk stages splits up unix pipe lines but only when you don't enter spaces to separate your commands in a unix pipe line. Commands such as sudo, effectively hide the real command that you are trying to run with more privileges, so you could have a debate about whether it was the sudo or the command following the sudo command that you thought was important.
How do you measure shell for loops? If I wanted to move a number of similar named files from one directory to another, I could either enter the mv command a number of times (a bit boring and time consuming) or I could write a one line for shell loop with a glob pattern to mv the files... -
Thanks,
Ryan -
What do you guys get when you list those as #root?
-
-
Code:
# history | awk '{print $2}' | awk 'BEGIN {FS="|"} {print $1}'|sort|uniq -c | sort -n | tail | sort -nr 135 zypper 66 rpm 34 cd 33 ls 24 YaST2 14 dmesg 11 mv 11 /etc/rc.d/smb 10 mount 8 wget
Your Top 10 Commands
Discussion in 'Linux Compatibility and Software' started by lupusarcanus, Apr 18, 2011.