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

Remove today's installed packages

Terminal - Remove today's installed packages
grep "install " /var/log/dpkg.log | awk '{print $4}' | xargs apt-get -y remove --purge
2009-04-06 13:06:04
User: skygreg
Functions: awk grep xargs
Remove today's installed packages


There is 1 alternative - vote for the best!

Terminal - Alternatives
grep -e `date +%Y-%m-%d` /var/log/dpkg.log | awk '/install / {print $4}' | uniq | xargs apt-get -y remove
2010-01-12 09:42:22
User: skygreg
Functions: awk grep uniq xargs
Tags: Debian

Adapted using your usefull comments !

Know a better way?

If you can do better, submit your command here.

What others think

it's safer to grep for today's date. SO, grep and awk part should be replaced with the following

grep -e `date +%Y-%m-%d` /var/log/dpkg.log | grep install | awk '{print $5}' | uniq

then add xargs

Without mentioning the date, all packages installed since login will be removed, if i'm not wrong.

Comment by alperyilmaz 399 weeks and 5 days ago

The --purge isn't necessary. If that was left out, you could at least experiment with the command without losing config files from packages that are to be deinstalled.

On my ubuntu system, dpkg seems to rotate the /var/log/dpkg.log file every month, so the above command would *purge* anything you installed this calendar month.

Comment by bwoodacre 399 weeks and 5 days ago

Another useless use of grep. How about taking advantage of awk?

awk '/install / {print $4}' /var/log/dpkg.log
Comment by atoponce 399 weeks and 4 days ago

Your point of view

You must be signed in to comment.