zsh-users
 help / color / mirror / code / Atom feed
From: Volodymyr Khomchak <kolombo.inc@gmail.com>
To: zsh-users@zsh.org
Subject: Re: find duplicate files
Date: Mon, 8 Apr 2019 18:14:24 +0300	[thread overview]
Message-ID: <35f7f111-f6f4-8df3-b19f-5177ac48e128@gmail.com> (raw)
In-Reply-To: <391277a7-d604-4c20-a666-a2886b1d2939@eastlink.ca>

Why wouldn't simple find work for this purpose ?
This example can do what you need

|find -not -empty -type f -printf "%s\n" | sort -rn | uniq -d | xargs -I{} -n1 find -type f -size {}c -print0 | xargs -0 
md5sum | sort | uniq -w32 --all-repeated=separate If you want something dedicated then look at *fdupes* utility |

On 4/8/19 5:58 PM, Ray Andrews wrote:
> Pardon a comment from the peanut gallery, but it seems strange to me that the issue of duplicate files would be 
> something that would not have been solved definitively  50 years ago.  I'd have thought that for donkey's years there 
> would be utilities that would let you find duplicates at various levels of rigour because it's so obviously an issue 
> that's bound to come up.  No?
>

  reply	other threads:[~2019-04-08 15:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-06  5:40 Emanuel Berg
2019-04-06 13:02 ` Paul Hoffman
2019-04-06 14:44   ` Emanuel Berg
2019-04-06 19:11     ` zv
2019-04-06 19:42       ` Emanuel Berg
2019-04-08 14:37         ` Paul Hoffman
2019-04-08 14:58           ` Ray Andrews
2019-04-08 15:14             ` Volodymyr Khomchak [this message]
2019-04-08 15:24             ` Peter Stephenson
2019-04-08 15:32             ` Andrew J. Rech
2019-04-08 15:47             ` Oliver Kiddle
2019-04-08 16:29               ` Ray Andrews
2019-04-08 16:45                 ` Bart Schaefer
2019-04-08 21:30               ` Emanuel Berg
2019-04-09  1:08             ` Jason L Tibbitts III
2019-04-09  1:28               ` Ray Andrews
2019-04-09  9:28               ` Charles Blake
2019-04-08 21:26           ` Emanuel Berg
2019-04-07 11:16       ` Charles Blake
2019-04-07 21:32         ` Bart Schaefer
2019-04-08 11:17           ` Charles Blake
2019-04-08 17:14             ` Bart Schaefer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=35f7f111-f6f4-8df3-b19f-5177ac48e128@gmail.com \
    --to=kolombo.inc@gmail.com \
    --cc=zsh-users@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).