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? I just tried this on Windows XP. On a FAT32 or a NTFS filesystem the inode is unchanged. On a FAT filesystem, it changes. I assume that means that FAT doesn't support a real file ID. The only thing I think anyone would be using FAT for these days is possibly a boot partition. That's the only reason I have one. I use to to multi-boot various flavors of Windows. It's the lowest common denominator. >I am not complaining even if that is the case. I just want to >understand what it does. NP. I complain about this fairly frequently myself. :-) cgf - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Fri Jan 20 14:36:27 2006
This archive was generated by hypermail 2.1.8 : 2006-01-20 14:36:38 EST