Subject: case insensitive inode number patch. Is this better?
From: [email-masked] (Scott Kempf)

2 Jan 1997 10:44:37 -0800
Sender: [email-masked]
Approved: [email-masked]
Distribution: cygnus
Message-ID: <[email-masked]>
Original-To: [email-masked]
Original-Sender: [email-masked]

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, 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.
Any ideas?

				Scott

*** cdksrc/src/winsup/syscalls.cc.orig	Mon Dec 30 17:45:27 1996
--- cdksrc/src/winsup/syscalls.cc	Tue Dec 31 14:59:29 1996
***************
*** 21,26 ****
--- 21,27 ----
  #include <fcntl.h>
  #include <pwd.h>
  #include <unistd.h>
+ #include <ctype.h>
  
  #include "winsup.h"
  
***************
*** 613,619 ****
    
    while (*name != '\0') 
      {
!       hash += *name + (*name <<17);
        hash ^= hash >> 2;
        name++;
      }
--- 614,620 ----
    
    while (*name != '\0') 
      {
!       hash += tolower (*name) + (tolower (*name) <<17);
        hash ^= hash >> 2;
        name++;
      }

----------------------------------
Scott Kempf ([email-masked])
Running gnu-win32 beta 17.1
under Windows 95.
-
For help on using this list, send a message to
"[email-masked]" with one line of text: "help".