X-Spam-Check-By: sourceware.org Date: Sun, 4 Dec 2005 09:29:40 -0800 From: Yitzchak Scott-Thoennes To: cygwin AT cygwin DOT com Subject: Re: open() giving ENOENT when trying to create files with control chars Message-ID: <20051204172940.GB3276@efn.org> References: <120220052038 DOT 3878 DOT 4390B0AC000B476600000F2622007601800A050E040D0C079D0A AT comcast DOT net> <20051202220905 DOT GA2999 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051202220905.GA2999@calimero.vinschen.de> User-Agent: Mutt/1.4.2.1i X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 On Fri, Dec 02, 2005 at 11:09:05PM +0100, Corinna Vinschen wrote: > On Dec 2 20:38, Eric Blake wrote: > > > I'm trying to create a file (on NTFS) with a CR in the name and getting > > > ENOENT; is it possible for this to work (without a managed mount)? > > > > Welcome to Windows. None of these non-portable characters are > > supported in filenames except in managed mounts. > > Just to push the point a bit, note the words "non-portable". I did do a bit of looking around before posting, and saw the *?/\<>|:" characters mentioned in several places, but not the 0-0x1f characters. Now, I've looked more and see those officially verboten as well. (Though I also saw a page that documents how 8.3 filenames are formed and seems to say that the *?/\<>|:" characters *are* possible in NTFS filenames.) http://support.microsoft.com/default.aspx?scid=kb;en-us;117258 is interesting... -- 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/