From: jazz@softway.com (Jason Zions) Subject: Re: POSIX semantics? 26 Jul 1997 13:17:54 -0700 Approved: cygnus.gnu-win32@cygnus.com Distribution: cygnus Message-ID: <33DA52BA.29A6.cygnus.gnu-win32@softway.com> References: <01BC9A13.3EAFDC60@sos> Reply-To: jazz@softway.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.01Gold (WinNT; I) Original-To: Sergey Okhapkin Original-CC: "gnu-win32@cygnus.com" Original-Sender: owner-gnu-win32@cygnus.com Is your E: NTFS or FAT? Local or remote? Which mkdir command were you running? One built to use the POSIX subsystem, or one built to Win32? One ported from a Unix box, or one written by MS programmers who still didn't quite believe it was reasonable to allow case-sensitive filenames? You can choose to believe me, or you can choose not to. Either way, the fact remains that the POSIX subsystem as shipped by Microsoft in NT 3.51 and NT 4.0 is quite capable of creating case-sensitive directory names. It wouldn't have passed the NIST PCTS were that not the case; I'm fairly certain something very much like this appeared in it. Running OpenNT 2.0 on an NTFS local drive: $ mkdir aaa AAA $ touch aaa/foo AAA/bar $ ls [aA]* AAA: bar aaa: foo $ uname -a Windows_NT SWING 4.0 SP0 Pentium Jason - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request@cygnus.com" with one line of text: "help".