On Thu, 8 Mar 2018, Samuel Sieb wrote:
On 03/08/2018 12:59 PM, Stephen Morris wrote:
> On 9/3/18 6:13 am, Todd Zullinger wrote:
>> Robert P. J. Day wrote:
>>> ... ah, so the replacement of those cross-directory hardlinks
>>> with symlinks will happen in F28, is that what you're saying?
>> The change will be in F28, yes. The few files in /usr/bin are
>> simply copied, not symlinked. Within /usr/bin, the identical
>> files are hardlinked to each other.
> I haven't been keeping up with this thread prior to now so I
> apologize if I'm covering old ground or have misinterpreted what
> this thread is saying. It is my understanding that currently when
> a file copied to any location, a physical copy is not produced,
> the copy is a hardlink to the original file, until such time as
> one of the "copies" is changed and then both become physical files
> with one file reflecting the pre-change contents, whereas the same
> doesn't happen with symlinks. Are you saying that with F28
> hardlinks are going to be replaced by symlinks, so that the
> hardlink functionality no longer works, or are you saying that
> symlink functionality is being changed to function the same as
> hardlinks, hence we lose the existing symlink functionality?
You definitely haven't been keeping up. :-)
This is a discussion about a specific package (git). It has a lot
of identical binary files with different names in two different
directories. Currently these are all hard linked to each other.
What will change is that the cross-directory hardlinks will be
that was my understanding -- as long as the files are within
precisely the same directory, hard links could still be used, but any
cross-directory links (even if within the same filesystem) will use
symlinks. is that about right?