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 Date: Fri, 30 Apr 2004 14:53:06 -0700 From: Yitzchak Scott-Thoennes To: cygwin AT cygwin DOT com Subject: Re: 20040422 snapshot and filenames ending with . (was: Re: errors using DB_File perl module under 20040422 snapshot) Message-ID: <20040430215306.GA1828@efn.org> References: <20040425191603 DOT GA2416 AT efn DOT org> <1661641065 DOT 20040426224002 AT familiehaase DOT de> <20040427093715 DOT GA3084 AT efn DOT org> <20040428190221 DOT GA1228 AT efn DOT org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040428190221.GA1228@efn.org> User-Agent: Mutt/1.4.1i Organization: bs"d X-IsSubscribed: yes On Wed, Apr 28, 2004 at 12:02:21PM -0700, Yitzchak Scott-Thoennes wrote: > On Tue, Apr 27, 2004 at 02:45:38AM -0700, Yitzchak Scott-Thoennes wrote: > > you can create files ending with a . which are > > not stat'able unless another file exists with the same name without > > the dot. (and even then rm on the dotted name removes the non-dotted > > file): > > > > $ cat >foo. > > bar > > ^D > > $ ls -l foo. > > ls: foo.: No such file or directory > > > > $ ls -l foo > > ls: foo: No such file or directory > > Would it help to try multiple snapshots and see where this broke? I > already had the 20040416 and 20040420 ones and they both fail (but > 1.5.9 is ok)? I was really hoping for a "already fixed in CVS" > response :), is there anything I can do to help track this down? This is fixed by the 20040430 snapshot; thanks, Corinna (though I wonder if it would be possible to consistently allow filenames to end in a . on ntfs, since it seems you can actually create separate "foo" and "foo."). -- 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/