Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Sun, 2 Jun 2002 12:33:24 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: stat(2) wierdness Message-ID: <20020602163324.GB12502@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <026901c20a46$245b0ad0$6132bc3e AT BABEL> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <026901c20a46$245b0ad0$6132bc3e@BABEL> User-Agent: Mutt/1.3.23.1i I guess it's time for my periodic "this is not a bug reporting mailing list" observation. If you are going to post here, there is an assumption that you have done more than just notice a bug. It's called "cygwin-developers" becuase the hope is that you will track down the problem more thoroughly than a normal cygwin mailing list message. Bug reports are fine in the cygwin mailing list. The bar is a little higher here. cgf On Sun, Jun 02, 2002 at 03:59:48PM +0100, Conrad Scott wrote: >This started out looking at the /proc filesystem, in particular XEmacs's >handling of the file /proc/registry/HKEY_CLASSES_ROOT/* but I got >distracted. > >Basically: the handling of filenames consisting of exactly one of these >win32 reserved characters, * ? " < >, is broken in the current CVS cygwin. >This has changed between 1.3.10-1 and the current release. (nb this is in >the standard filesystem, not the /proc filesystem.) > >For example, stat(2) succeeds for filenames containing of a single * ? " < >or >, claiming that they are directories. (It correctly rejects filenames of >a single | and I'm ignoring \ and : since I'm unclear what should happen >with these anyhow.) These were all rejected in 1.3.10-1. > >This gives lovely wierdness if you try something like: >$ cp /etc/passwd '*' >cp: cannot create regular file `*/passwd': No such file or directory > >After this little diversion, back to XEmacs wierdness.