From: Christopher Faylor <me@cgf.cx>
Date: Fri, 20 Jan 2006 15:40:55 GMT
Subject: Re: [PATCH] "sleep 1" sleeps too little on cygwin
Message-ID: <20060120154054.GA3392@trixie.casa.cgf.cx>
In-Reply-To: <81b0412b0601200723k1a271046u9c310d9c9b7d83f0@mail.gmail.com>

On Fri, Jan 20, 2006 at 04:23:10PM +0100, Alex Riesen wrote:
>On 1/20/06, Christopher Faylor <me@cgf.cx> wrote:
>> On Thu, Jan 19, 2006 at 05:13:17PM -0800, Junio C Hamano wrote:
>> >Christopher Faylor <me@cgf.cx> writes:
>> >>Inodes are only calculated by hashing the path name when the OS lacks
>> >>the support to provide a "real" inode and in that case there is no hard
>> >>link support available so it's a non-issue.
>> >
>> >Does that mean on such filesystems "mv foo bar" would change the i-num
>> >of the moved entity?
>
>It is just a rename. It will not change inode by definition (the file is the
>same, it is the name which was changed). To get inode change you
>have to create it, like "cp foo bar; rm foo". And now, if a filesystem
>has (or exports) inodes, would the inode change. If it does not, you
>really can't say anything about the inode (it can even change, and
>does in this case, being calculated from pathname).
>
>> I just tried this on Windows XP.  On a FAT32 or a NTFS filesystem the
>
>I have FAT32. It does not support inodes"
>    $ : > foo
>    $ stat foo |grep node
>    Device: 111712fch/286724860d    Inode: 3595119992080318288  Links: 1
>    $ mv foo bar
>    $ stat bar |grep node
>    Device: 111712fch/286724860d    Inode: 3595119974866484701  Links: 1

Ok, I must have been hallucinating.  I just tried it again.  It doesn't
work on FAT32.

cgf