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 Message-Id: <5.1.0.14.0.20020605152947.08add3a0@pop.ma.ultranet.com> X-Sender: lhall AT pop DOT ma DOT ultranet DOT com Date: Wed, 05 Jun 2002 15:33:31 -0400 To: Michael Eager , Cygwin Mailing List From: "Larry Hall (RFK Partners, Inc)" Subject: Re: DOS Special Names In-Reply-To: <3CFE6697.C041242@mvista.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 03:29 PM 6/5/2002, Michael Eager wrote: >I've run into a problem creating a regular file with the name >COM20000. I can create this file from Windows, either using >fopen() or in a Command window, but not when using Cygwin. >Windows does prevent creating files named COMx, where x is a >single digit. > >The code in winsup/cygwin/path.cc checks to see if the file >name is COM followed by any integer, not just a single digit. >Is this intentional or an error? > >Shouldn't Cygwin check to see if there is an installed driver >named COM (or AUX, etc.) rather than just assume that all COMxxxx >are supposed to be devices? I agree that it makes sense for Cygwin not to restrict more file names than Windows does. Feel free to submit a patch for this, if you're so inclined. Larry Hall lhall AT rfk DOT com RFK Partners, Inc. http://www.rfk.com 838 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/