Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sourceware.cygnus.com
Message-ID: <3701067B.D4F1B50C@acm.org>
Date: Tue, 30 Mar 1999 18:14:35 +0100
Reply-To: Ing.-Buero_Heller@t-online.de
MIME-Version: 1.0
To: cygwin@sourceware.cygnus.com
Subject: RE: B20: mv deletes files on error (NT)
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
From: Ing.-Buero_Heller@t-online.de (Martin Heller)

Beware: NTFS itself IS case-sensitive  WIN32 is not ...
this leads to the question: should 'mv' on cygwin know the difference
between FAT/NTFS
filesystem and should it make a difference between 'foo' and 'Foo' on
NTFS ?

excerpt rom MS-SDK:
...The following POSIX-compliant features are included in NTFS:
Case-sensitive naming. Under POSIX, README.TXT, Readme.txt, and
readme.txt are all different files.
Hard links. A file can be given more than one name. This allows two
different filenames, which can be
located in different directories, to point to the same data.
Additional time stamps. These show when the file was last accessed or
modified.
Caution
POSIX applications create case-sensitive filenames where two or more
filenames can differ only in case
(for example, annm.doc and AnnM.Doc).
While NTFS supports both case-preservation and case-sensitivity, you
cannot use standard commands
with NTFS to manage filenames that differ only in case. (Standard
commands include those used at the
command-line — such as copy, del, and move — and their File Manager
equivalents.)
For example, both annm.doc and AnnM.Doc are deleted if you type the
following at the command prompt:
del AnnM.Doc
You must use POSIX applications to manage filenames that differ only in
case.
For related information, see the section on the POSIX subsystem in
Chapter 1, "Windows NT Architecture"
and Chapter 17, "POSIX Compatibility." ....


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com