hi,
On Sun, 18 Sept 2022 at 21:39, Thomas Schmitt <scdbac...@gmx.net> wrote:
> Will Mengarini wrote:
> > Note that the file-type character "h" (the leftmost character in your
> > second line of output) isn't documented ...
> The 'h' probably comes from {...}
> which converts tar file type LNKTYPE to 'h'.
thanks. (yes, no documentation..)
> It's tar which does it by the (dev,ino) comparison in dump_hard_link().
> I have a test case from xorriso development: ...
> $ tar cf - test/hardlinks | tar tvf -
> drwxr-xr-x thomas/thomas 0 2009-05-18 19:57 test/hardlinks/
> -rw-r--r-- thomas/thomas 42786 2008-11-14 09:44 test/hardlinks/x
> hrw-r--r-- thomas/thomas 0 2008-11-14 09:44 test/hardlinks/hardlink_x
> link to u/test/hardlinks/x
_thank you_. another question, if you don't mind: what will happen
if I extract such an archive on a "normal" computer with ext3/4
filesystems? (don't want to .. experiment with this)
> The question remains why jr's tar records two files with the same path
> as a pair of hardlinks. (I place my bet on btrfs snapshots.)
the "machine" is a VM, pre-installed by Google, and it has more mounts
than dog has fleas :-) (but '/' says is on btrfs)
