commandlinefu.com is the place to record those command-line gems that you return to again and again.
Delete that bloated snippets file you've been using and share your personal repository with the world. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.
If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/
You can sign-in using OpenID credentials, or register a traditional username and password.
First-time OpenID users will be automatically assigned a username which can be changed after signing in.
Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.
» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10
Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):
Subscribe to the feed for:
somewhat faster version to see the size of our directories. Size will be in Kilo Bytes. to view smallest first change '-k1nr' to '-k1n'.
There are 4 alternatives - vote for the best!
using mb it's still readable;) a symbol variation
$ du -ms {,.[^.]}* | sort -nk1
Found this one little more for me. This one removes the perl dependency (from command 2535).
Source for command : http://www.earthinfo.org/linux-disk-usage-sorted-by-size-and-human-readable/
If you can do better, submit your command here.
You must be signed in to comment.
ncdu (package name:ncdu) is also nice if you find yourself needing to do this repeatedly and/or interactively.
So, why not just:
du -k | sort -nr@0JM, We have lot of way to display size, but I think 'find' is handling Tree traverse better than others. '-depth' is pretty good here, It makes 'du' first calculate inner directories then when outer directories comes, kernel cache helping 'du' to do faster calculation.
@mohan43u Yeah, there are multiple ways, but the find/exec combination is slow as hell.
Try yourself:
First, create some test-directories:
for n in `seq 1 1 10`; do for m in `seq 1 1 10`; do mkdir -p $n/$m; done; doneThen check performance:
time find . -depth -type d -exec du -s {} \; | sort -k1nr >/dev/nullreal 0m0.398s
user 0m0.136s
sys 0m0.239s
time du -k | sort -nr > /dev/nullreal 0m0.025s
user 0m0.007s
sys 0m0.018s
Case closed.