X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Sat, 12 Feb 2011 19:12:24 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Preremove/postinstall scripts fail with snapshot installed Message-ID: <20110212181224.GC3264@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4D55A88E DOT 3090301 AT cornell DOT edu> <20110212142555 DOT GB5682 AT calimero DOT vinschen DOT de> <4D56A002 DOT 2090707 AT cornell DOT edu> <4D56A7D5 DOT 6010104 AT cornell DOT edu> <20110212164415 DOT GB3264 AT calimero DOT vinschen DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20110212164415.GB3264@calimero.vinschen.de> User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Feb 12 17:44, Corinna Vinschen wrote: > On Feb 12 10:31, Ken Brown wrote: > > I just did a system restore to undo the last round of Windows > > updates, and the problem went away. I'm not sure where to go from > > here. > > You're right, I can reproduce it on W7 32 and 64 bit. > [...] > So this problem occurs on Windows 7 and perhaps Vista only with recent > Cygwin snapshots or current CVS, only with the latest security updates > installed and, for some reason, only when calling postinstall scripts > from setup.exe. Calling the same scripts from an interactive bash works > fine. > > The 2010-10-18 snapshot is the snapshot which reintroduced the ability > to remove in-use directories by accessing an undocumented structure in > Vista/Windows 7. Looks like MSFT had to change something which breaks > an application using this structure in a very specifc scenario, which is > unfortunately exposed by running bash from setup.exe :-( > > By installing the security updates again, one by one, I figure out > that it is the security update connected to KB 2393802 which triggers > the problem. > > But, be it as it is, it doesn't make sense to ask people not to install > the security updates, so I fear it's "back to the drawing board" for > Cygwin. Sigh. Just FYI, I have a working workaround. It's not exactly how I would like to handle this stuff, but at least we know there *is* a solution which still maintains the desired ability to delete an in-use directory. Stay tuned. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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