Make hardlinking kernel-devel optional

Chris Adams cmadams at
Wed Feb 1 04:12:29 UTC 2006

Once upon a time, Jeremy Katz <katzj at> said:
> It does it so that you ensure that you're only hardlinking the same copy
> of any foo.h in the directory layout instead of all copies

Why?  hardlink isn't going to replace files that are different, so there
is no gain in not letting hardlink link all copies that are the same.

It is smart enough to look at the stat() info before reading the
contents for comparison, so files of different sizes aren't going to be
compared just because they have the same name.

The whole point of running hardlink is to reduce disk usage; why not let
it try to do the best job possible?
Chris Adams <cmadams at>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.

More information about the devel mailing list