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

Generate SHA1 hash for each file in a list

Terminal - Generate SHA1 hash for each file in a list
find . -type f -exec sha1sum {} >> SHA1SUMS \;
2009-10-05 18:33:59
User: gpenguin
Functions: find sha1sum
2
Generate SHA1 hash for each file in a list

All output is placed in file SHA1SUMS which you can later check with 'sha1sum --check'. Works on most Linux distros where 'sha1sum' is installed.

Alternatives

There is 1 alternative - vote for the best!

Terminal - Alternatives
ls [FILENAME] | xargs openssl sha1
2009-10-03 02:05:43
User: m00dimus
Functions: ls xargs
1

List files and pass to openssl to calculate the hash for each file.

find . -regex ".*\(avi\|mp4\|wmv\)$" -print0 | xargs -0 sha1sum
sha1sum * >> SHA1SUMS
2010-05-05 18:14:52
User: manny79
Functions: sha1sum
-2

Alternative command for performing an sha1 hash for a given set of files matched by a wildcard

Know a better way?

If you can do better, submit your command here.

What others think

I believe in bash this will append the output of the find command to SHA1SUMS rather than each invocation of sha1sums appending to the file (-exec doesn't use a shell to run sha1sums). Here the result is the same either way but worth mentioning.

Comment by bwoodacre 271 weeks and 4 days ago

Sorry, but I disagree. I just ran it and the SHA1SUMS file contains a list of files with their SHA1 hashes...same as 'md5sum'. Within 'find', everything up to the "\;" is used as the command to execute. Per the 'man find' page:

"All following arguments to find are taken to be

arguments to the command until an argument

consisting of ?;? is encountered."

HOWEVER, the man page does state the behavior of {} in find is different in other flavors of 'find'. So there are probably other differences with other flavors as well.

Comment by gpenguin 271 weeks and 3 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts