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:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=qmTjBOhbALWMNVdD
	skS4JT/Ph9V/BUEih5Fy/dvGTXwA/+GzwbOOdZtKyw/fMnRCafFhXJhmWc4h+XRR
	B6QsoAdmh8A3Mnhe7Q0H/dJJon6wBOBjQ+Rga5kr4fbViwdTW8TRjb6ZgrFeW7br
	rYDnYB9qFhtk7BiWrenXSQaZZXI=
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:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; s=default; bh=XxlWjK3IX+3QnMtXFNlsmq
	vsveQ=; b=D8zgI/n/aLhKkFAun0mmDjAU7mjbwHvF0rXc3VrFI5TAQKEQPjq50R
	EOMxAz2rxhTuKZEMQMFQmpqaremuP40kghkAtnQAYHwncMGglroxBexbsZaAKI3K
	nVgI0OEZsrZkiDO1W+C/h5z4nuPtPTRkhnxyUoXEfu3yYePhzQ/kc=
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=4.0 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT,SPF_SOFTFAIL autolearn=no version=3.3.2 spammy=H*UA:Bat!, H*x:Bat!, H*F:D*yandex.ru, luck
X-HELO:	smtp.ht-systems.ru
Date:	Sat, 2 Jan 2016 18:33:19 +0300
From:	Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To:	cygwin AT cygwin DOT com
Message-ID:	<1710491599.20160102183319@yandex.ru>
To:	Bryan Henry <bryanhenry AT mac DOT com>, cygwin AT cygwin DOT com
Subject:	Re: Question about incorrect System path from cygpath with case-sensitivity enabled
In-Reply-To:	<B9C70902-5C7E-4AC6-A63A-583DCEC2771C@mac.com>
References:	<B9C70902-5C7E-4AC6-A63A-583DCEC2771C AT mac DOT com>
MIME-Version:	1.0
X-IsSubscribed:	yes

Greetings, Bryan Henry!

> I enabled (some time ago, not recently) case sensitivity on my Windows 8.1
> system by setting the registry key mentioned in the FAQ here:
> https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive

> Today, I updated Cygwin and noticed a message about a failed postinstall
> script at the end. Here's the excerpt from setup.log.full showing
> /etc/postinstall/base-files-mketc.sh exiting early:

> 2016/01/01 15:45:32 running: C:\cygwin\bin\bash.exe --norc --noprofile
> "/etc/postinstall/base-files-mketc.sh"
> Directory /C/WINDOWS/System32/drivers/etc does not exist; exiting
> If directory name is garbage you need to update your cygwin package
> 2016/01/01 15:45:32 abnormal exit: exit code=1

> Since this was an existing installation, that postinstall script failing
> isn't a big deal since the symlinks that it would normally create already
> exist, but I wanted to dig into why it's failing in the first place in case
> it is a symptom of something bigger. Taking a look at that script and trying
> "/usr/bin/cygpath -S -u" for myself, I see now why it failed:

> [~]$ cygpath -S -u
> /C/WINDOWS/System32
> [~]$ file `cygpath -S -u`
> /C/WINDOWS/System32: cannot open `/C/WINDOWS/System32' (No such file or directory)
> [~]$ file /C/Windows/System32
> /C/Windows/System32: directory

> I get similar results from "cygpath -W". It seems that cygpath has not
> picked up on the fact that the directory is really "Windows" and not
> "WINDOWS",

cygpath uses system calls to return the directories you're asking for.
If a system call return wrong case, cygpath can't do anything to amend it.
You have to fix your system first, then it will just work.

> which is of course important in my case with case sensitivity
> enabled.

The problem is that you have it enabled. Windows was not built with this
setting in mind.
Very little amount of native Windows programs would expect it to be enabled.

> I'm not sure if this is a failure of cygpath directly or perhaps a
> piece of configuration elsewhere that needs to get updated in addition to
> the registry key change mentioned in the FAQ. Can anyone offer any
> recommendations to fix the Windows path returned by cygpath, or is this a bug?

You have to also change all registry keys containing mismatched paths.
Good luck.


-- 
With best regards,
Andrey Repin
Saturday, January 2, 2016 18:29:45

Sorry for my terrible english...


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