From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20905 invoked by alias); 7 Nov 2016 16:17:31 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 20887 invoked by uid 89); 7 Nov 2016 16:17:30 -0000 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 Received: from ishtar.tlinx.org (HELO Ishtar.sc.tlinx.org) (173.164.175.65) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 07 Nov 2016 16:17:29 +0000 Received: from [192.168.3.12] (Athenae [192.168.3.12]) by Ishtar.sc.tlinx.org (8.14.7/8.14.4/SuSE Linux 0.8) with ESMTP id uA7GHNjL061830 for ; Mon, 7 Nov 2016 08:17:26 -0800 Message-ID: <5820A668.9070606@tlinx.org> Date: Mon, 07 Nov 2016 16:17:00 -0000 From: "L. A. Walsh" User-Agent: Thunderbird MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Windows 10 updates causes fork retry no child processes References: <581A0AA5.5030107@verizon.net> <0d98a082-e270-659f-5b48-b9dfd01fc85f@SystematicSw.ab.ca> <581AD3D3.2020908@verizon.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2016-11/txt/msg00057.txt.bz2 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