Util-Linux package development
 help / color / mirror / Atom feed
From: Ruediger Meier <sweet_f_a@gmx.de>
To: Karel Zak <kzak@redhat.com>
Cc: "util-linux" <util-linux@vger.kernel.org>, Kevin Fenzi <kevin@scrye.com>
Subject: Re: hardlink util -- files de-duplication
Date: Fri, 1 Jun 2018 15:08:38 +0200	[thread overview]
Message-ID: <201806011508.38470.sweet_f_a@gmx.de> (raw)
In-Reply-To: <20180601113807.ghf6dtcd5xa6qptu@ws.net.home>

On Friday 01 June 2018, 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? ;-)

+1

>
>    https://src.fedoraproject.org/cgit/rpms/hardlink.git/

The original and almost identical repo is this:
  https://pagure.io/hardlink.git

I've CC'ed the project admin Kevin Fenzi.

> It's one .c file.
>
> Comments & objections?
>
>     Karel

  reply	other threads:[~2018-06-01 13:08 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 [this message]
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
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=201806011508.38470.sweet_f_a@gmx.de \
    --to=sweet_f_a@gmx.de \
    --cc=kevin@scrye.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox