X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Sun, 1 Mar 2009 10:47:13 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [1.7] rebaseall doesn't solve the problem
Message-ID: <20090301094713.GA10046@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <499F6682 DOT 1090204 AT cwilson DOT fastmail DOT fm> <20090224100616 DOT GC6035 AT calimero DOT vinschen DOT de> <49A85971 DOT 6070300 AT cwilson DOT fastmail DOT fm> <20090228104337 DOT GG19887 AT calimero DOT vinschen DOT de> <49A986B4 DOT 2080501 AT cwilson DOT fastmail DOT fm> <20090228195127 DOT GA26646 AT ednor DOT casa DOT cgf DOT cx> <20090228202850 DOT GB8503 AT calimero DOT vinschen DOT de> <49A9ACDD DOT 8010806 AT cwilson DOT fastmail DOT 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 AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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 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/