Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Dave Korn" To: Subject: RE: Slight problem with case sensitivity on managed mounts with C VS-1.11.6 Date: Thu, 22 Jul 2004 18:30:08 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-reply-to: Message-ID: X-OriginalArrivalTime: 22 Jul 2004 17:30:08.0328 (UTC) FILETIME=[88B11C80:01C47011] > -----Original Message----- > From: cygwin-owner On Behalf Of Hughes, Bill > Sent: 22 July 2004 17:24 > From: Ronald Landheer-Cieslak Sent: 22 July 2004 16:49 > > ..snip.. > > > OK, the problem is with CVS - the managed mounts are > working properly. > > CVS assumes Cygwin is/runs on a case-insensitive > (file)system, which is > > usually the case. On managed mounts, however, the > assumption fails, and > > CVS complains about conflicts in file names that do not exist. (I > > thought this was clear from the original post, but > apparently, that was > > not the case..) > ObNitPick: > NTFS _is_ case sensititve, but Windows isn't. ObUltraPedanticNitPick: No it isn't. NTFS is case *preserving*; neither NTFS nor windoze are case *sensitive*. > If you use the native API you can create foo.bar and FOO.BAR > in the same directory. ObDoesn'tWFM: dk AT mace /> cd /win/c/test-case/ dk AT mace /win/c/test-case> ls -lart total 0 drwxr-xr-x+ 2 dk Domain U 0 Jul 22 18:21 . drwxrwxr-x+ 35 Administ SYSTEM 0 Jul 22 18:22 .. dk AT mace /win/c/test-case> touch //./c:/test-case/foo.bar dk AT mace /win/c/test-case> ls -lart total 0 drwxrwxr-x+ 35 Administ SYSTEM 0 Jul 22 18:22 .. -rw-r--r-- 1 dk Domain U 0 Jul 22 18:25 foo.bar drwxr-xr-x+ 2 dk Domain U 0 Jul 22 18:25 . dk AT mace /win/c/test-case> touch //./c:/test-case/FOO.BAR dk AT mace /win/c/test-case> ls -lart total 0 drwxrwxr-x+ 35 Administ SYSTEM 0 Jul 22 18:22 .. drwxr-xr-x+ 2 dk Domain U 0 Jul 22 18:25 . -rw-r--r-- 1 dk Domain U 0 Jul 22 18:25 foo.bar dk AT mace /win/c/test-case> I am right that using the //./ notation invokes the NtCreateFile function, aren't I? I think that's why the syntax works for deleting NUL files and so on, so it ought to work in this case too, shouldn't it? > > Yes, the problem is with CVS, not with Cygwin. Personally, > I though the > > first paragraph of the original post made that clear - > apparently, it > > didn't, so I apologize. > OT but possibly of interest, case-sensitivity (or otherwise) > and how to > handle it has been a topic of some heated debate on the subversion and > tortoisesvn maling lists on and off. Consensus on how to > handle this has > proved, shall we say, 'elusive'. My ${CURRENCY_UNIT}*1e-2: rather than guessing, cvs should *find out*, by creating a file in the current directory using a name that is known not to exist, try to unlink it using a shifted version of that name, and then see if it's gone or not. I *think* that would do the job, wouldn't it? cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/