X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Bill Hughes <bill DOT hughes AT cgi-europe DOT com>
Subject:  Re: open() giving ENOENT when trying to create files with control chars
Date: Mon, 5 Dec 2005 11:20:35 +0000 (UTC)
Lines: 37
Message-ID:  <loom.20051205T120121-877@post.gmane.org>
References:  <120220052038 DOT 3878 DOT 4390B0AC000B476600000F2622007601800A050E040D0C079D0A AT comcast DOT net> <20051202220905 DOT GA2999 AT calimero DOT vinschen DOT de> <20051204172940 DOT GB3276 AT efn DOT org> <20051204194350 DOT GG2999 AT calimero DOT vinschen DOT de> <loom DOT 20051205T110754-387 AT post DOT gmane DOT org> <20051205103043 DOT GN2999 AT calimero DOT vinschen DOT de>
Mime-Version:  1.0
Content-Type:  text/plain; charset=us-ascii
Content-Transfer-Encoding:  7bit
User-Agent: Loom/3.14 (http://gmane.org/)
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:

> 
> On Dec  5 10:11, Bill Hughes wrote:
..snip..
> > Uh, don't forget this is the NTFS API and not the Windows API.
> > If you want to go down this route you may as well add case sensitive file
> > names too...
> 
> That's not quite right.  Case-sensitivity is a flag which can be
> switched on and off at will.  It's a property of the driver, not the
> underlying file system.  The underlying file system is obviously capable
> of storing case-sensitive filenames, the driver just handles characters
> only differing by case as equal in the default Windows case.  The above
> is converting invalid characters to valid characters.  These new
> characters are still valid characters even when you're working in a
> plain ASCII (or ISO-8859) environment, since NTFS stores the filenames
> in UNICODE anyway.
OK, I wasn't aware that you could persuade windows to use the case-sensitive
abilities of NTFS without hacking.
I'm not sure it would be obvious that the FS is capable of case sensitive
operations if we didn't already know that - to me it's equally obvious that FAT
isn't capable of these. Unless I'm wrong again of course.

> I'm not sure until I tried it, of course, but I don't think this will
> result in problems with Windows, just because your standard font can't
> display the characters.
Agreed, not on an NTFS filesystem anyway.
I tend to use FAT at home for dual boot machines so I can access the windows
disks read/write from linux as the ntfs write ability has had warnings attached
for a long time. Come to that I use fat for my XP box so I can use a linux
rescue cd when it goes wrong, hence my concerns about cygwin adding value to
NTFS ops that wouldn't apply to FAT.

Sorry if this is just noise,
Bill



--
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/