From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3979 invoked by alias); 22 Apr 2008 11:12:23 -0000 Received: (qmail 3967 invoked by uid 22791); 22 Apr 2008 11:12:23 -0000 X-Spam-Check-By: sourceware.org Received: from aquarius.hirmke.de (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Tue, 22 Apr 2008 11:12:05 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id 03E056D4312; Tue, 22 Apr 2008 13:12:02 +0200 (CEST) Date: Tue, 22 Apr 2008 11:12:00 -0000 From: Corinna Vinschen To: cygwin-apps@cygwin.com Subject: Re: [HEADSUP] Let's start a Cygwin 1.7 release area Message-ID: <20080422111202.GK23852@calimero.vinschen.de> Reply-To: cygwin-apps@cygwin.com Mail-Followup-To: cygwin-apps@cygwin.com References: <20080415183856.GM23852@calimero.vinschen.de> <4804FB2D.6040802@byu.net> <4805645E.63ED0505@dessent.net> <20080416084447.GN23852@calimero.vinschen.de> <20080421140428.GA7301@calimero.vinschen.de> <20080421174811.GZ23852@calimero.vinschen.de> <20080421201510.GE23852@calimero.vinschen.de> <480D7F83.300AE579@dessent.net> <480DA0EA.C5601934@dessent.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <480DA0EA.C5601934@dessent.net> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com X-SW-Source: 2008-04/txt/msg00273.txt.bz2 On Apr 22 01:25, Brian Dessent wrote: > I suppose I didn't state my point very well. Yes, there are Cygwin > tools for manipulating the registry. But the registry is an > implementation detail, and you should not need to know anything about > registry keys to uninstall Cygwin. At the moment this can be > accomplished via "umount -A" (and "cygrunsrv -R") with zero knowledge of > where the mount table happens to be implemented, or that there even is a > registry. > > With the mount table no longer stored in the registry, we will have no > way around saying "you must remove such-and-such key from the > registry." This is bad, IMHO. > > A separate issue is that even if we document a proper procedure for > removing Cygwin (as we currently do in the FAQ), users often don't read > manuals and just plunge in and try to delete stuff. They fail because > they forgot to stop services first, or because they don't understand > file ACLs. By adding a new key in the registry we make it increasingly > likely that in their fervor to dive in and delete things without reading > docs they will miss yet another step. I want to finally solve this for > good by making a program that encapsulates all this knowledge so that > they don't have to RTFM, and so that they just have a nice thing to > click on like every other well-behaved Windows program. I think it's > been a requested feature more than once. Btw., I think that an uninstall option would be a good thing. While I talked about the cyglsa DLL in my reply to Chuck on the Cygwin ML, it occured to me that this would be a job for the uninstaller as well: If the cyglsa DLL has been added to the registry value HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Authentication Packages it's not possible to remove the DLL unless you reboot. So, what the uninstaller would have to do is to remove the substring which contains "cyglsa.dll" or "cyglsa64.dll" from the above registry value and then to add the DLL to the PendingFileRenameOperations registry value. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat