X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Wed, 15 Feb 2012 10:42:36 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: PROGRAMFILES variable is not set during openssh session
Message-ID:	<20120215094236.GO25918@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<1329064411 DOT 16602 DOT 15 DOT camel AT arcfi-laptop> <20120213140712 DOT GD32512 AT calimero DOT vinschen DOT de> <1253729885 DOT 20120214044940 AT mtu-net DOT ru> <20120214082759 DOT GA20357 AT calimero DOT vinschen DOT de> <20120214090820 DOT GC20357 AT calimero DOT vinschen DOT de> <1692518632 DOT 20120215012013 AT mtu-net DOT ru>
MIME-Version:	1.0
In-Reply-To:	<1692518632.20120215012013@mtu-net.ru>
User-Agent:	Mutt/1.5.21 (2010-09-15)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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 15 01:20, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
> 
> >> > >> PROGRAMFILES variable is not set during openssh session.
> >> > >> This is very important for remote administrative tasks.
> >> > 
> >> > > OpenSSH 6.0p1 is due soon.  I asked to apply a patch upstream so that
> >> > > PROGRAMFILES is added back to the environment variables passed over
> >> > > to the child process.
> >> > 
> >> > Both of them? (on x86_64 systems, there's two relevant variables)
> >> 
> >> Argh.  Can of worms.  No, only the 32 bit variant for now.
> 
> > Oh, btw., 32 bit processes only see the 32 bit PROGRAMFILES variable
> > by default.  Which makes sense since PROGRAMFILES for 32 bit processes
> > is the same as PROGRAMFILES for 64 bit processes...
> 
> I can't say that I understood your reply, I'll just go into hiding thinking
> that you know what you doing >.>

A dangerous assumption... ;)

I think my reply was a bit on the strange side.  Let's use the source
instead.  If you start a 32 bit CMD on an English system you get this:

  ProgramFiles=C:\Program Files (x86)
  ProgramFiles(x86)=C:\Program Files (x86)

In the 64 bit CMD you get this:

  ProgramFiles=C:\Program Files
  ProgramFiles(x86)=C:\Program Files (x86)
    
So for a 32 bit process, the values of ProgramFiles and
ProgramFiles(x86) are identical.


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

- Raw text -