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:
This also works on non-Linux machines. If you have GNU sed you can do it more elegantly:
ifconfig | sed -n 's/^\s*inet \(addr:\)\?\([^\s]*\) .*/\2/;T;/^127\./d;p'
Shows only IP-addresses of ifconfig except 127.0.0.0/8.
I fixed the script to work on more systems and configs
short info
/inet/!d; #grep inet
/127.0/d; # grep -v 127.0
/dr:\s/d; # grep -v dr:
s/^.*:\(.*\)B.*$/\1/ # remove everything exept between : and B
I've been using it in a script to build from scratch proxy servers.
Simple and easy. No regex, no search and replace. Just clean, built-in tools.
Interfaces like lo can be omitted from the beginning, there are probably better ways of doing this, i'm a noob at awk.
I prefer the ip command to ifconfig as ifconfig is supposedly going to be deprecated. Certain IP address aliases can only be seen with the ip command (such as the ones applied by RHCS).
If you are interested in interfaces other than eth0 you will need to change eth0 to your interface name.
You could use this mammoth to nab the ip4 addresses of all your interfaces
perl -e '@_=`ifconfig -a`; sort(@_); foreach(@_) { /(inet addr\:)(\d+.\d+.\d+.\d+ )/; $_=$2; @uniq=grep($_ ne $prev && (($prev) = $_), @_);} print join "\n",@uniq,"\n"; '
it seems silly to have all this code when the following will work fine
ifconfig -a | grep "inet " | awk -F":" ' { print $2 } ' | cut -d " " -f1
Sometimes, you don't really care about all the other information that ifconfig spits at you (however useful it may otherwise be). You just want an IP. This strips out all the crap and gives you exactly what you want.