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:
Could use your ssh bash history if your known_hosts are hashed and you want to keep it hashed
There is 1 alternative - vote for the best!
Stop tormenting the poor animal cat. See http://sial.org/howto/shell/useless-cat/.
Edit:
replaced
sort | uniq
by
sort -u
Add to your bash profile to minimize carpal tunnel syndrome.
Doesn't work with user@hostname but appending "-l user" works fine if needed.
Works for ping as well..
complete -W "$(echo `cat ~/.ssh/known_hosts | cut -f 1 -d ' ' | sed -e s/,.*//g | uniq | grep -v "\["`;)" ping
I use this in my bashrc to expand hosts defined in ~/.ssh/config:
function _ssh_completion() {
perl -ne 'print "$1 " if /^Host (.+)$/' ~/.ssh/config
}
complete -W "$(_ssh_completion)" ssh
Here's a great article on how to setup your own ~/.ssh/config:
http://blogs.perl.org/users/smylers/2011/08/ssh-productivity-tips.html
If you have a lot of hosts in /etc/hosts this would be very useful. Anyone have any more concise examples?
Simple and fast variant, not using external programs. Another variation:
complete -W "$(while read line; do echo ${line%%[, ]*}; done < ~/.ssh/known_hosts)" ssh
HashKnownHosts must be off, of course.
If you can do better, submit your command here.
You must be signed in to comment.
or you could set your hosts in .ssh/config
You just blew the purpose of a hashed known_hosts files with the history. It may protect you against bots, thats all.