From: Carlos Santos <casantos@datacom.com.br>
To: "Aurélien Aptel" <aaptel@suse.com>
Cc: Karel Zak <kzak@redhat.com>, util-linux <util-linux@vger.kernel.org>
Subject: Re: hardlink util -- files de-duplication
Date: Wed, 6 Jun 2018 09:02:27 -0300 (BRT) [thread overview]
Message-ID: <781894140.1411342.1528286547497.JavaMail.zimbra@datacom.com.br> (raw)
In-Reply-To: <87lgby1vvn.fsf@suse.com>
> From: "Aur=C3=A9lien Aptel" <aaptel@suse.com>
> To: "Karel Zak" <kzak@redhat.com>, "util-linux" <util-linux@vger.kernel.o=
rg>
> Sent: Friday, June 1, 2018 10:25:48 AM
> Subject: Re: hardlink util -- files de-duplication
> Karel Zak <kzak@redhat.com> writes:
>> Comments & objections?
>=20
> Not objecting but I feel like I should mention there are multiple
> well-established alternatives:
>=20
> https://github.com/tobiasschulz/fdupes
> http://freedup.org/
> https://rdfind.pauldreik.se/
> https://github.com/markfasheh/duperemove
Compared to hardlink, fdupes has a richer feature set (e.g. dedupsoft
links). FreeDup has its own life and does not seem to be adoptable.
Dupremove is a complex software which requires glib2 and sqlite3.
--=20
Carlos Santos (Casantos) - DATACOM, P&D
=E2=80=9CMarched towards the enemy, spear upright, armed with the certainty
that only the ignorant can have.=E2=80=9D =E2=80=94 Epitaph of a volunteer
next prev parent reply other threads:[~2018-06-06 12:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 11:38 hardlink util -- files de-duplication Karel Zak
2018-06-01 13:08 ` Ruediger Meier
2018-06-01 20:20 ` Kevin Fenzi
2018-06-02 0:00 ` Francisco J. Tsao Santin
2018-06-01 13:25 ` Aurélien Aptel
2018-06-01 13:45 ` Samuel Thibault
2018-06-06 12:02 ` Carlos Santos [this message]
2018-06-01 13:29 ` Dmitry V. Levin
2018-06-12 10:55 ` Karel Zak
2018-06-12 11:22 ` Ruediger Meier
2018-06-12 12:12 ` Karel Zak
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=781894140.1411342.1528286547497.JavaMail.zimbra@datacom.com.br \
--to=casantos@datacom.com.br \
--cc=aaptel@suse.com \
--cc=kzak@redhat.com \
--cc=util-linux@vger.kernel.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.