Hide

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.


If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/

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.

Hide

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:

Hide

News

2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.
Hide

Tags

Hide

Functions

Verify MD5SUMS but only print failures

Terminal - Verify MD5SUMS but only print failures
md5sum --check MD5SUMS | grep -v ": OK"
2009-10-02 05:21:17
User: gpenguin
Functions: grep md5sum
6
Verify MD5SUMS but only print failures

All valid files are withheld so only failures show up. No output, all checks good.

Alternatives

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

This was the default behaviour of md5um(1) many years ago, only errors was reported, and if you wanted to see the good ones, add -v. It was changed to display everything by default, and the -v option disappeared. The change is extremely annoying, as it breaks with a fundamental UNIX philosophy: Be quiet. Don't say that things is OK, only report errors, because it's _those_ files you're interested in. And it's inefficient, as there might be thousands of lines generated by md5sum which is of no use and has to be filtered away.

Comment by sunny256 258 weeks and 4 days ago

SHA-1 is more secure than MD5 and is rapidly becoming the new industry standard. Use sha1sum instead of md5sum. That said, any integrity checking is better than none!

Comment by savanik 257 weeks and 5 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts