X-Spam-Check-By: sourceware.org
Date: Mon, 12 Dec 2005 10:49:52 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: open() giving ENOENT when trying to create files with control chars
Message-ID: <20051212094952.GD17517@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <120920050031 DOT 22095 DOT 4398D06400029F6F0000564F22070009530A050E040D0C079D0A AT comcast DOT net> <20051209074355 DOT GC5144 AT efn DOT org> <43993754 DOT 2CA4F6B8 AT dessent DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <43993754.2CA4F6B8@dessent.net>
User-Agent: Mutt/1.4.2i
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

On Dec  8 23:50, Brian Dessent wrote:
> Yitzchak Scott-Thoennes wrote:
> 
> > > Windows strips trailing spaces and dots (unless the file name
> > > consists only of spaces).  You need a managed mount to
> > > preserve those; otherwise "foo ", "foo.", "foo. . . . ", "foo",
> > > and a bunch of other spellings all refer to the same file.
> > 
> > I attempted to indicate in the message above that I tried it and
> > succeeded in using filenames with spaces on the end (and *different*
> > files named the same except without the spaces).  It seems this is
> > *not* an across-the-board Windows limitation.
> 
> This is probably a difference in the win32 API versus the native API.

Correct.  In the native API you can create practically every filename
which doesn't use invalid characters.  But these filenames are not
compatible with Win32 functions.  Since the bulk of Cygwin is still
using the Win32 API, we can't afford to create Win32 incompatible
filenames.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat, Inc.

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