From: "Dmitry V. Levin" <ldv@altlinux.org>
To: Karel Zak <kzak@redhat.com>
Cc: Alexey Gladkov <legion@altlinux.org>,
util-linux <util-linux@vger.kernel.org>
Subject: Re: hardlink util -- files de-duplication
Date: Fri, 1 Jun 2018 16:29:30 +0300 [thread overview]
Message-ID: <20180601132930.GA5803@altlinux.org> (raw)
In-Reply-To: <20180601113807.ghf6dtcd5xa6qptu@ws.net.home>
[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]
On Fri, Jun 01, 2018 at 01:38:07PM +0200, Karel Zak wrote:
> For last 17 years in Red Hat based distros is available hardlink(1)
> util, man hardlink:
>
> hardlink traverses one or more directories searching for duplicate
> files. When it finds duplicate files, it uses one of them as the
> master. It then removes all other duplicates and places a hardlink
> for each one pointing to the master file. This allows for
> conservation of disk space where multiple directories on a single
> filesystem contain many dupli‐ cate files.
>
> ...
>
> the util is little bit orphaned, what about to add this util to
> util-linux to make it available for another distros and keep it
> maintained in serious way? ;-)
>
> https://src.fedoraproject.org/cgit/rpms/hardlink.git/
>
> It's one .c file.
>
> Comments & objections?
Better late than never.
BTW, our hardlink package has some Owl patches applied,
please remind us to rebase and submit them. ;)
--
ldv
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2018-06-01 13:29 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
2018-06-01 13:29 ` Dmitry V. Levin [this message]
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=20180601132930.GA5803@altlinux.org \
--to=ldv@altlinux.org \
--cc=kzak@redhat.com \
--cc=legion@altlinux.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox