public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "L. A. Walsh" <cygwin@tlinx.org>
To: cygwin@cygwin.com
Subject: Re: Windows 10 updates causes fork retry no child processes
Date: Mon, 07 Nov 2016 16:17:00 -0000	[thread overview]
Message-ID: <5820A668.9070606@tlinx.org> (raw)
In-Reply-To: <c7eebf5f-9f33-f5ae-70e7-da586f687725@t-online.de>

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

  parent reply	other threads:[~2016-11-07 16:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-02 15:47 Gerry Reno
2016-11-02 17:31 ` Evgeny Grin
2016-11-03  0:05   ` Gerry Reno
2016-11-03  5:06 ` Brian Inglis
2016-11-03  6:06   ` Gerry Reno
2016-11-03  7:02     ` Marco Atzeri
2016-11-03 13:01     ` Brian Inglis
2016-11-03 13:42       ` Gerry Reno
2016-11-03 13:46         ` Eliot Moss
2016-11-03 17:08           ` Brian Inglis
2016-11-03 14:31     ` Hans-Bernhard Bröker
2016-11-03 14:58       ` Gerry Reno
2016-11-03 17:28         ` Brian Inglis
2016-11-03 18:33           ` Gerry Reno
2016-11-03 18:47             ` Achim Gratz
2016-11-03 19:02               ` Gerry Reno
2016-11-03 19:11                 ` Achim Gratz
2016-11-03 22:08             ` Brian Inglis
2016-11-03 22:28               ` Gerry Reno
2016-11-04 18:40               ` Achim Gratz
2016-11-05  0:25                 ` Gerry Reno
2016-11-07 16:17       ` L. A. Walsh [this message]
2016-11-03  9:13 ` Marko Božiković

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5820A668.9070606@tlinx.org \
    --to=cygwin@tlinx.org \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).