X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:content-transfer-encoding
	:content-type:message-id:date:from:reply-to:to:subject
	:references:in-reply-to; q=dns; s=default; b=cyiGE9YtOFjoVeotIlA
	0cMQUCHiONpEgJ5g0Syq9VlQU7QGfFCOcaBOsKgjkWmuX+cAqvQAxAxtzrzul5tM
	YNdEi5xjx8DWMpND3TtiAKQ/6+O7LTh7GruELOTqTssUWlkcTVC/yosTsB9ddbdy
	SIdMCAHRFdRQW3RpL2EuU0+c=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:content-transfer-encoding
	:content-type:message-id:date:from:reply-to:to:subject
	:references:in-reply-to; s=default; bh=LOqgLMAdgOXJZyqnkCMHj02i8
	dQ=; b=CBK6OnNds/MBDnkN0xJpzwe5WybgET3hGM0hQ0L9S4PCZgvxRQR3Y7AAp
	vQCZ41lk6fJ3YZ0m2DdXjw0ia/f60VDpbpeNlbGumbaORdG0IsOH09n47p2u2jS5
	4g6217D7e6fP8/utnq/97ZZx0nkJ/j6ejh2iFr6eaSueP9aXVI=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-1.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO:	vms173007pub.verizon.net
MIME-version:	1.0
Message-id:	<525E95F9.5050701@cygwin.com>
Date:	Wed, 16 Oct 2013 09:34:49 -0400
From:	"Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-to:	cygwin AT cygwin DOT com
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
To:	cygwin AT cygwin DOT com
Subject:	Re: [x86_64 on W7] Cannot remove cygwin root directory
References:	<CAPw2spiGQfRpi8A1AO6oTuTAJ-iUZgTUMBeQMnTo8RFfuyW-NQ AT mail DOT gmail DOT com> <525E7D3C DOT 20808 AT cornell DOT edu> <CAPw2spg4HS4XEidbYOD8sPp1XmPypk7Ffj_26BgcUP_EPiW3Xw AT mail DOT gmail DOT com>
In-reply-to:	<CAPw2spg4HS4XEidbYOD8sPp1XmPypk7Ffj_26BgcUP_EPiW3Xw@mail.gmail.com>

On 10/16/2013 8:19 AM, Frédéric Bron wrote:
>> There is an upstream packaging bug that caused two copies of the README file
>> to be installed, one of which is called "README." (including the dot).  I
>> guess Windows is confused by whatever Cygwin does to allow file names to
>> include a dot.  But you can delete the file from a Cygwin bash shell.
>
> Thanks a lot. I reinstalled a minimum cygwin in another directory and
> could rm -rf the old cygwin root directory.
> This is strange that cygwin can remove something Windows cannot...

Not at all.  Historically, going back to 8.3 DOS file name days, the "dot"
wasn't stored as part of the name.  So "name" and "name." were the same.
"cmd.exe" still maintains compatibility with this historical behavior.
However, Cygwin uses an API that makes the distinction, so "name" and
"name." are different.

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
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 -