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:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=WF
	3gvkoQLeWdFb4LmCb+O+QSem9nN0H0HIXUSB6l3Sywd5GQ5Z8gzo0x1CAv+oXcQL
	9K+KKnIXt1ZdKgpY6YaCFGoJ/9GN9GITJM2XDQofmxfrgNKDw8Vrsks1OZzaTPcF
	uXh4WNR+Ggp2f7xAsDD6ZKaP4acpT/pOCaypVj8KI=
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:in-reply-to:references:date
	:message-id:subject:from:to:content-type; s=default; bh=TL+G3NKW
	hlAvbGF78Fm2mWCIwVs=; b=rvXxF3UVkt6iBlO1/pZRwabrzKAyX0zXZASnThui
	+bSRI7MzrxXlvkLjNocNKGEt/JZF0FowqwoBaSqKgcvMpsqKDh722NQj7Ww7v0bQ
	u1LfNNZISvIG2E+4sC41sQT733JMSUGdeqAbf0Cv1oVOh/cMFZwx3TBEgiSRRQeB
	PKI=
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=2.7 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=stromekonexgode, stromeko AT nexgo DOT de, achim, Achim
X-HELO: mail-ig0-f176.google.com
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20130820;        h=x-gm-message-state:mime-version:in-reply-to:references:date         :message-id:subject:from:to:content-type;        bh=TPJ2pQ1XQP6MVvTHCJqDYNH9aB8W1A2pt+45pRD7ev4=;        b=QO01/C/GFdwKRVLBZLuy22zk7nie66WXP2zFEt+T3ATGSqeQMVdf52ba4jQz4eRKDp         M3myeyYWDrvffE1G1Rl9lEBht6sJqvTjo0VvdOwFPlyHT8Gk2CQAL+Trj9fH1Mxrk0Ue         2kwZGTHvsu45m7ODCdhExb0JC1xJ+Aot3cFkKIFjRZ7sgiolkBe7bxQtW1MSiUQoGGWV         o2su/e5RleA1KcZ4lmOFEHWLrodfAgYVDe5UFInsWAfT93QvPJ2lxgw1urReZAIYE7Y0         WrwA5BnzBMgK8Hwq+WqEHJhSlXUzdSpuEGZn2CzARxcs9Nh8Eq5oJbYqmBD7N//Dgt4Y         LXjw==
X-Gm-Message-State: AG10YOQJcBc39zHYdJVouqHcXu8AR6JnKjtTlgwWMR8Ms0Hl3yc79Zww0EudvWparfuuzGR/E/OB4R1IVMa9iQ==
MIME-Version: 1.0
X-Received: by 10.50.90.180 with SMTP id bx20mr26389396igb.67.1453883369366; Wed, 27 Jan 2016 00:29:29 -0800 (PST)
In-Reply-To: <loom.20160122T080836-250@post.gmane.org>
References: <CALiPeun3bCr9uNNA56Kc-8VbLXFXrTrTWJikdRx0jjRFvAuwkA AT mail DOT gmail DOT com>	<loom DOT 20160120T085800-407 AT post DOT gmane DOT org>	<loom DOT 20160120T135441-652 AT post DOT gmane DOT org>	<87fuxsjd5x DOT fsf AT Rainer DOT invalid>	<loom DOT 20160120T215934-785 AT post DOT gmane DOT org>	<87k2n290bh DOT fsf AT Rainer DOT invalid>	<CALiPeuk2KE9B81qU-YZhTYUXgQEFiE4TTxm_-kFnORMH+wON+Q AT mail DOT gmail DOT com>	<loom DOT 20160122T080836-250 AT post DOT gmane DOT org>
Date: Wed, 27 Jan 2016 16:29:29 +0800
Message-ID: <CALiPeu=NknUV=Ze=T7wFQSjDu24V2BvmhqwX7rQDGtA=ctg6+w@mail.gmail.com>
Subject: Re: Base-files-mketc.sh error for non-existing C:\Windows\SysWOW64\drivers\etc
From: David Lee <mailtolky AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes

On 22 January 2016 at 15:13, Achim Gratz <Stromeko AT nexgo DOT de> wrote:

> What I mean is this: are all the Windows versions that Cygwin supports
> looking for the hosts and other files in
>
>   %windir%\system32\drivers\etc
>
> or are there some versions, situations or configurations where it looks for
> those files in a different place?

There are two issues here:

(1) A bug that the base-files script tries to link to files in
    C:\Windows\SysWow64\Drivers\Etc directory (should have been
    C:\Windows\System32\Drivers\Etc).

(2) Your concern of whether there are 'other places to look
    for those files'.

It seems that you want to wait for confirmations/denials for (2) before
fixing (1). If there is none then (1) stays forever. I think it is better to
separate two issues.

First, fix (1) as if (2) doesn't exist (if you have problem
with this then consider: the old code is coded as if (2) doesn't
exist, why should the patched code be different?)

Then, wait for confirmations for (2). You can always patch again if a
confirmation emerges - it is never too late. If no answer comes up,
at least the bug doesn't stay forever.

David Lee.

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