From:	jqb AT netcom DOT com (Jim Balter)
Subject:	Re: case insensitive inode number patch, is this better?
10 Jan 1997 18:58:48 -0800 :
Sender:	daemon AT cygnus DOT com
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<32D6F133.3056.cygnus.gnu-win32@netcom.com>
References:	<199701101644 DOT KAA29829 AT utig DOT ig DOT utexas DOT edu>
Mime-Version:	1.0
X-Mailer:	Mozilla 3.01Gold (WinNT; I)
Original-To:	Scott Kempf <scottk AT utig DOT ig DOT utexas DOT edu>
Original-CC:	gnu-win32 AT cygnus DOT com
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

Scott Kempf wrote:
> 
> Here is a questionable patch.  Win95 doesn't have any inode numbers,
> so they are faked using a hash of the file's name.  This is very
> creative, but not the best idea.  I don't have a better solution,
> but it seems to me that the hash should not be case sensitive,
> since the file system isn't.  This patch makes the inodes case
> insensitive.  I'm not aware of any problem it fixes,

I am; cp x X will now complain instead of leaving x (X) as an empty
file.  There are other programs that check for file identity that would
likewise benefit.  *Obviously* different names for the same file
should produce the same inode number.

> but it does
> create one:  "mv x X" now fails with "mv: `x' and `X' are the same file".
> Since they are the same file, the error is somewhat reasonable.

This is mv's fault for being too restrictive.  It should trust the
rename systenm call, the cygwin version of which should do the
rename properly.  In any case, mv without the patch doesn't complain
but it doesn't do the rename, either!

> Any ideas?

Better to make inode numbers 1-1 with files than to worry about
the mv case.

--
<J Q B>
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -