X-Spam-Check-By: sourceware.org Message-ID: <43993754.2CA4F6B8@dessent.net> Date: Thu, 08 Dec 2005 23:50:44 -0800 From: Brian Dessent MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: open() giving ENOENT when trying to create files with control chars References: <120920050031 DOT 22095 DOT 4398D06400029F6F0000564F22070009530A050E040D0C079D0A AT comcast DOT net> <20051209074355 DOT GC5144 AT efn DOT org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com 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 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. Brian -- 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/