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:
Quick and dirty one-liner to get the average ping(1) time from a server.
when we work with terminal often we open man pages for help if we did some mistakes
and when we want to open the man page for command we are working with this one helps
as many people may be knowing that '!!' performs the last command action
we use it in sudo !! to perform the last action with root previleages
man !! will also be helpful and handy
thanx
If you want to copy all files listed (with full path) in a text-file (i.e. cmus playlist.pl) to a certain directory use this nice oneliner...
Credits goes to RiffRaff: http://www.programmingforums.org/post242527-2.html
alternative to tr char '\012'
works with sed's that don't accept "\n"
allows for multi-char sentinals, while tr(1) only operates on single chars
i686 = 32 bits
x86_64 = 64 bits
the command "getconf LONG_BIT" will work just as well.
You can use this in shell scripts to show which commands are actually run. Just prepend every "critical line" with "v˽".
$TMP=/tmp
echo "Let me create a directory for you"
v mkdir $TMP/new
In scripts this can be more useful than "set -x", because that can be very verbose with variable assignments etc.
Another nice use is if you prepend every "critical" command with "v", then you can test your script by commenting out the actual execution.
Build an awk array with all commands and then select a random one at the end.
This avoids spawning extra processes for counting with wc or generating random numbers.
Explicitly call /bin/ls to avoid interactions with aliases.
Useful in while and if statements
if not grep string filename; then echo string not found; exit 1; fi
This command is useful for separating a text file where all the words are in one line. Any group of spaces will be replaced with a single newline. Instead of one long line of tokens. You'll have a long list of tokens. One token per line.
This can be used in scripts, to find out the origin of target IP etc.