The user would also click on the Comparison Options tab to specify the sort of comparison to be run. In DoubleKiller, the general idea was that the user would click on the Scan Options tab (at top left) to name the folders to be compared to specify files (e.g., file.txt) or file types (e.g., f*.txt), with the option to either exclude those from the search or (just the opposite) to limit the search to only those files or types to ignore, exclude, or limit the search to files of a certain size and/or with certain attributes (e.g., read-only) and so forth. In this image, we have a screenshot of DoubleKiller on the left and dupeGuru on the right, both running in Windows 10 (double-click to enlarge):Īs the image illustrates, DoubleKiller offered a denser listing than dupeGuru. This side-by-side comparison image may provide a sense of the difference. I had also concluded that, for my purposes, dupeGuru was not a serious competitor against DoubleKiller. In previous searches, I had repeatedly seen that dupeGuru was considered among the best Linux tools for this purpose. Perhaps I should begin by explaining what I was looking for, by describing a bit of my usage of DoubleKiller in Windows. It seemed that I would have to find duplicate detection software written for Linux.
As described in the post reporting on that effort, I had unfortunately found that DoubleKiller performed poorly in Wine. I had recently tried to run DoubleKiller in Linux using Wine. As part of that process, I was interested in finding Linux software that could detect duplicate files. As described in another post, I was in the process of developing a ransomware-resistant backup system that relied, in part, on a Linux system.
0 kommentar(er)
