What's this?

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.

Get involved!

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.

Universal configuration monitoring and system of record for IT.

Stay in the loop…

Follow the Tweets.

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

Subscribe to the feeds.

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:



May 19, 2015 - A Look At The New Commandlinefu
I've put together a short writeup on what kind of newness you can expect from the next iteration of clfu. Check it out here.
March 2, 2015 - New Management
I'm Jon, I'll be maintaining and improving clfu. Thanks to David for building such a great resource!

Top Tags



Psst. Open beta.

Wow, didn't really expect you to read this far down. The latest iteration of the site is in open beta. It's a gentle open beta-- not in prime-time just yet. It's being hosted over at UpGuard (link) and you are more than welcome to give it a shot. Couple things:

  • » The open beta is running a copy of the database that will not carry over to the final version. Don't post anything you don't mind losing.
  • » If you wish to use your user account, you will probably need to reset your password.
Your feedback is appreciated via the form on the beta page. Thanks! -Jon & CLFU Team

Replicate a directory structure dropping the files

Terminal - Replicate a directory structure dropping the files
for x in `find /path/ -type d | cut -b bytesoffoldername-`; do mkdir -p newpath/$x; done
2009-03-06 20:07:51
User: f4nt
Functions: cut mkdir
Replicate a directory structure dropping the files


There are 2 alternatives - vote for the best!

Terminal - Alternatives
find . -type d -exec mkdir -p $DESTDIR/{} \;
find . -type d -print0 | (cd $DESTDIR; xargs -0 mkdir)
2010-11-18 09:33:51
User: rocketraman
Functions: cd find xargs

Here is how to replicate the directory structure in the current directory to a destination directory (given by the variable DESTDIR), without copying the files.

Know a better way?

If you can do better, submit your command here.

What others think

This is a great command, worked for me like a charm!!! Thanks I have been looking for this for a long time..

Comment by zaipai 420 weeks and 5 days ago

Ouch. Backticks. The only thing they offer is portability. If this command is to be run on the severely ancient and outdated Bourne shell, then you're fine. Otherwise, you should use the more readable and more capable $().

for x in $(find /path/ -type d | cut -b bytesoffoldername-); do mkdir -p newpath/$x; done
Comment by atoponce 420 weeks and 4 days ago

Neat idea. Cut could be used a little more gracefully though. If your directory separators are forward slashes, '/', then you could ask cut to not cut out bytes (characters) but any number of directory names that you specify. Here I set the delimiter as '/' and ask for all directory names after the first.

find path -type d | cut -d / -f 2-
Comment by bwoodacre 420 weeks and 1 day ago

I added an alternative that doesn't use that ugly cut...

Comment by rocketraman 331 weeks and 6 days ago

Your point of view

You must be signed in to comment.