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/
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.
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
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:
All output is placed in file SHA1SUMS which you can later check with 'sha1sum --check'. Works on most Linux distros where 'sha1sum' is installed.
There is 1 alternative - vote for the best!
List files and pass to openssl to calculate the hash for each file.
Alternative command for performing an sha1 hash for a given set of files matched by a wildcard
If you can do better, submit your command here.
You must be signed in to comment.
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.
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.