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:
There are 2 alternatives - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
I like this use of tar and use it a lot on local machines to copy entire directory trees to some other place...
e.g.: tar cpf - . | (cd /somewhere/else; tar xvf -)
I suppose this can work the other way with:
tar cpf - . | ssh somehost 'cd /some/directory && tar xvpf -'
perhaps use tar xvBf - to ensure a good copy. B performs re-blocking.
Its worth mentioning that if you have links in the directory tree you are copying then check them after the copy. Soft links may break if pointing outside the directory tree being copied. Hard links will copy the 'pointed at' files... good, but bad if huge.
great command...
Nice. However in most cases scp -r should do the same and is a bit easier to type.
ha.... true scp -r will work too :)
For cases where scp -r doesn't work properly, there's rsync, as in:
rsync -av user@somemachine:somedir .Of course, rsync tries to use 'rsh' by default. To get it to use ssh, use either
RSYNC_RSH=`which ssh` rsync -av user@somemachine:somedir .or
rsync --rsh=`which ssh` -av user@somemachine:somedir .