Does a search and replace across multiple files with a subgroup replacement.

Very quick! Based only on the content sizes and the character counts of filenames. If both numbers are equal then two (or more) directories seem to be most likely identical.

if in doubt apply:

AWK function taken from here:

http://stackoverflow.com/questions/2912224/find-duplicates-lines-based-on-some-delimited-fileds-on-line

This command will traverse all of the folders and subfolders under current working directory. For every file inside it, it will do a search inside the content of the file for a specific term 'what'. Then it will print a list of the lines that contain that term (and match that pattern). Each matching line will be preceded with the path and name to the file and then the line number iside taht file wehre the pattern was found. Then the actual content of the matching lien will be printed.

The output will be piped throug less, so that the user can scroll through it if it goes beyond the limits of the current display window.

If you need to find some pictures on your disk but excluding some path.

recurse through all files, get the message hash, flip the output as filename, hash value

Use find's built-in "exec" option to avoid having to do any weirdness with quoting.

Will move in that case every file in the current folder older than 30 days to the "old" folder

Replace "mv $i old/" by any command such as rm / echo to do something different.

This command uses -newerXY to show you the files that are modified since a specific date. I recommend looking for "-newerXY" on the manpage to get the specifics.

Adapted from http://stackoverflow.com/questions/1358540/how-to-count-all-the-lines-of-code-in-a-directory-recursively#answer-1359246

Will find and list all core files from the current directory on. You can pass | xargs rm -i to be prompted for the removal if you'd like to double check before removal.

Check all bash scripts in current dir for syntax errors WITHOUT running them.

Use find's internal stat to get the file size then let the shell add up the numbers.

Using find's internal stat to get the file size is about 50 times faster than using -exec stat.

Find files and calculate size with stat of result in shell