Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 09 Mar 2023 17:00:58 +0700
From:      Olivier <Olivier.Nicole@cs.ait.ac.th>
To:        Michael Schuster <michaelsprivate@gmail.com>
Cc:        guru@unixarea.de, pho@freebsd.org, steve@sohara.org, questions@freebsd.org
Subject:   Re: problem while moving HOME from FreeBSD to MacOS with bsdtar
Message-ID:  <wu7wn3q8crp.fsf@banyan.cs.ait.ac.th>
In-Reply-To: <CADqw_gKqHTn3rKiQ1ZrD4Bbfb-spuR4Vy-6vbdfw_K7qbTOk1A@mail.gmail.com> (message from Michael Schuster on Thu, 9 Mar 2023 10:55:30 %2B0100)

next in thread | previous in thread | raw e-mail | index | archive | help
> I read that differently: it's a single entry (see 'ls -li' further
> up), but matches any case:
>
>> $ ls -li Homework HOMEWORK
>> 4016236 -rw-r--r--  1 apitzm  OCLC\Domain Users  0  9 M=C3=A4r 09:37 HOM=
EWORK
>> 4016236 -rw-r--r--  1 apitzm  OCLC\Domain Users  0  9 M=C3=A4r 09:37 Hom=
ework

In Unix parlance, it is called a link (or a hard link): two filenames
(possibly in two different directories, but must be in the same file
system) sharing a single inode.

That is completely normal, but that should not be what is created by tar
-x (or by touch) by default.

Bests,

Olivier



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?wu7wn3q8crp.fsf>