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 packages by pattern on debian and based systems

Terminal - Remove packages by pattern on debian and based systems
sudo apt-get remove --purge `dpkg -l | awk '{print $2}' | grep gnome` && apt-get autoremove
2009-04-28 10:34:42
User: kelevra
Functions: awk grep sudo
Remove packages by pattern on debian and based systems

Useful for removes a package and its depends, for example to remove the gnome desktop environment, also configuration files will be removed, you should be carefully and sure that you want to do this.


There is 1 alternative - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

a command every debian user running gnome should use :)

Comment by GinoMan2440 425 weeks and 5 days ago

and ubuntu!

Comment by GinoMan2440 425 weeks and 5 days ago

except you also want to add...

apt-get install kde
Comment by GinoMan2440 425 weeks and 5 days ago

hehe, I prefer lite window managers, but I think that is very useful when you are just testing other apps ;)

Comment by kelevra 425 weeks and 5 days ago

I grow weary of the kde evangelism going on in the last couple days.

PS- you can use apt-get autoremove --purge all in one go. No need for the second apt-get autoremove command ;)

Comment by linuxrawkstar 425 weeks and 4 days ago

There are virtual packages that just contain dependencies for just what you're trying to do manually. I prefer doing this inside aptitude, where I can interactively see what's about to be removed, etc. This is especially useful when there are broken packages, or the dependencies have changed as is sometimes the case on a debian testing system.

Comment by bwoodacre 425 weeks and 4 days ago

apt-get remove --purge gnome~n


Comment by unixmonkey8034 228 weeks and 2 days ago

Your point of view

You must be signed in to comment.