Dimitrios Apostolou wrote:
But when the tarball is extracted, two files with same inode are created, which is kind of unexpected behaviour - at least for me
Other utilities have similar behavior (e.g., ls, cp, du), in that they pretend the symlink isn't there and behave as if the pointed-to inode is there directly. Tar's current behavior is compatible with these other utilities, whereas its old behavior was incompatible.
