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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	q=dns; s=default; b=wgpQTFDu9oWWwFs2TpjfnZHT+FwSTpky0TbA6tmLqSO
	4ab36DThof2H6hINCnlQtpDfQcB+pNhXVhVemIl5qIKjRjYZ73QHXyKOFyOtVeDn
	Es0T4XqHpFCpLLUeDGW1o6eDsow3RREIl/kZlndeyGecyVjamF8vsnRazE926VHs
	=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	s=default; bh=c8b8+8Y5lku0GvynChGkJ+99tJ8=; b=q3mMIdTDx5wYBwTFV
	P+9NteZ1AzG0xg7kdnExoJ/aKP3nBmMrTz/I0w2wdq1QUcLSCRZzZc35uKjPH8M5
	tTYUNnx2/uN33rPjeNCpC+GJBUwHTMj8V+qHijgonPRdjGlJ9qsaEZsxU9C8SKoC
	qCTeaWkz+eK3aaWl0oqkS9BYMw=
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.0 required=5.0 tests=BAYES_50,RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=damage, constantly, H*r:192.168.3, dll
X-HELO:	Ishtar.sc.tlinx.org
Message-ID:	<5820A668.9070606@tlinx.org>
Date:	Mon, 07 Nov 2016 08:06:00 -0800
From:	"L. A. Walsh" <cygwin AT tlinx DOT org>
User-Agent:	Thunderbird
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Windows 10 updates causes fork retry no child processes
References:	<581A0AA5 DOT 5030107 AT verizon DOT net> <0d98a082-e270-659f-5b48-b9dfd01fc85f AT SystematicSw DOT ab DOT ca> <581AD3D3 DOT 2020908 AT verizon DOT net> <c7eebf5f-9f33-f5ae-70e7-da586f687725 AT t-online DOT de>
In-Reply-To:	<c7eebf5f-9f33-f5ae-70e7-da586f687725@t-online.de>
X-IsSubscribed:	yes

Hans-Bernhard Bröker wrote:
> Am 03.11.2016 um 07:06 schrieb Gerry Reno:
>> What is needed is for Cygwin itself to detect and manage the situation.
> 
> That is technically impossible.  The DLL rebasing procedure can only be 
> done from _outside_ Cygwin.
---
	Oh?
	The Dll rebasing needs to be done outside of the hosted
cygwin environment, which is not to say that dll rebasing is done
outside of cygwin.  I don't know about now, but everything to do
dll-rebasing was part of cygwin -- just not the hosted environment
part of it.  

	For example "setup.exe" is part of the cygwin project,
but not part of the hosted environment, so it can replace dll's
that are part of the hosted environment (or tell you that you
will need to reboot).

	None of the above discussion over terminology should
be taken to mean that I believe cygwin should constantly try
to repair actively changing damage done by win10.  
	

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