delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2010/03/01/10:51:30

X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Mon, 1 Mar 2010 16:51:16 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Directory named "." created at /: seems to have happened during update
Message-ID: <20100301155116.GA13891@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <4B8BDC2C DOT 20406 AT bonhard DOT uklinux DOT net>
MIME-Version: 1.0
In-Reply-To: <4B8BDC2C.20406@bonhard.uklinux.net>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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 Mar  1 15:24, Fergus wrote:
> >> On Windows XP I can't reproduce it either.  Hmm.
> 
> Windows XP SP3 is what I'm using.
> 
> >> Are you sure the directory name is really "."?
> 
> Yes. I tried various mechanisms for testing this such as
> 
> dir ". "
> rename ". " "mydir"
> 
> etc all to  no avail. And also I see the / after the listing:
> 
> ls -al /m
> total 16
> drwxr-xr-x  14 fergus ver_1.5    0 Jan  1  1970 ./
> drwxr-xr-x  14 fergus ver_1.5    0 Jan  1  1970 ./
> drwxr-xr-x  15 fergus ver_1.5    0 Jan  1  1970 ../
> <etc etc>
> 
> The following is just a stream of findings.

This is really weird.  I tested originally on NTFS but now that you
mentioned FAT32, I tested this on FAT32.  The result is that the
NtCreateFile function does *not* return an error, but afterwards there
is no file or directory called ".", except for the default "." directory
entry.  That's a relieve for me, but it's weird nevertheless.
NtCreateFile gets called with the FILE_CREATE disposition, which should
have returned some "file already exists" type of status code...

Anyway, I have checked in a patch to setup.exe so that "." and ".."
path components are filtered out of the path before it's used in
OS calls.  This should at least avoid these annoying "unable to extract"
message dialogs which potentially appear with these paths.

> 3. Whatever the disk management history, and whether or not Cygwin
> triggered the problem, simply being able to generate the output
> 
> ls -al /m
> total 16
> drwxr-xr-x  14 fergus ver_1.5    0 Jan  1  1970 ./
> drwxr-xr-x  14 fergus ver_1.5    0 Jan  1  1970 ./
> drwxr-xr-x  15 fergus ver_1.5    0 Jan  1  1970 ../
> <etc etc>
> 
> show that something is VERY WRONG INDEED.

The filesystem is apparently broken for whatever reason.  A good
time to switch to NTFS ;)

Btw., it would be nice if you could reply to the thread rather then
starting a new thread for the same topic.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019