From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12203 invoked by alias); 1 Mar 2009 09:47:30 -0000 Received: (qmail 12193 invoked by uid 22791); 1 Mar 2009 09:47:29 -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.43rc1) with ESMTP; Sun, 01 Mar 2009 09:47:24 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id 9F4BA6D418D; Sun, 1 Mar 2009 10:47:13 +0100 (CET) Date: Sun, 01 Mar 2009 09:47:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: [1.7] rebaseall doesn't solve the problem Message-ID: <20090301094713.GA10046@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <499F6682.1090204@cwilson.fastmail.fm> <20090224100616.GC6035@calimero.vinschen.de> <49A85971.6070300@cwilson.fastmail.fm> <20090228104337.GG19887@calimero.vinschen.de> <49A986B4.2080501@cwilson.fastmail.fm> <20090228195127.GA26646@ednor.casa.cgf.cx> <20090228202850.GB8503@calimero.vinschen.de> <49A9ACDD.8010806@cwilson.fastmail.fm> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49A9ACDD.8010806@cwilson.fastmail.fm> User-Agent: Mutt/1.5.19 (2009-02-20) 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 X-SW-Source: 2009-03/txt/msg00001.txt.bz2 On Feb 28 16:30, Charles Wilson wrote: > Corinna Vinschen wrote: > > Only exes require the TS-aware bit. Two interesting snippets from MSDN: > > > > http://msdn.microsoft.com/en-us/library/cc834995(VS.85).aspx > > But in order to set this flag without problems cropping up, you must > satisfy: > > * The application does not run as a system service (that is, LUID=System). > > This probably isn't an issue for cygwin-1.7 and beyond, given the > changes in how services are installed. (Dang, I need to release an > updated csih...) I don't think you will get problems even if you're running a Cygwin application as system service. I don't know the exact reason for this rule, but all the TS-aware rules usually have something to do with "don't change anything which might break the same application running in another user context." These rules don't have POSIX applications in mind. > * The application does not write to the HKEY Local Machine registry hive > for user specific data or configuration. > > Hmm. regtool? /proc/registry? Hmm, regedit? You're taking these rules too literally, imho. > Either way, you lose. If we go one way, then you can't use regtool or > /proc/registry to manipulate the virtualized registry entries, if you're > trying to fix something related to a non-TS (windows) app. If we go the > other way, then you can't use regtool or /proc/registry to manipulate > the "real" non-virtualized registry. Cygwin applications won't use the virtualized registry keys anyway. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/