X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:references:to:from:reply-to:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=FPNAcJHckUaP5LRp
	1q56/yTmW9+HujyMP7A8T5mDvGAvG+t1JS5J47+EJw8GwMstnvOyT0F+TVYwc5LF
	+h6VS0NLXI31dp9jKiCL54LLX7R71Qhwmu7aZB8BOQoRn6XQcECnCvaO2YaN9hSA
	J/HTS9RI46rxLGTEwLCFzDnAK2o=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:references:to:from:reply-to:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=35fbSuG1M4+wvcopId3irE
	UK/zI=; b=EY6jShwsZryjog6n1NTcCd6GuOPWDphplBsb3DwjAwrF0BIJr6icN7
	g5tDdo42twqk9ecssKfa4BwMCmI0C0SGUJduS+8eq0TLj34cPquNNeMZXY8gRqaU
	5sOEjwMek5IdnVR0oYLEiIIjEIJFtkhbW2cUuBQfuuD3Ayg9115I4=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=1.1 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=Hx-spam-relays-external:sk:smtp-ou, Hx-spam-relays-external:shaw.ca, H*r:shaw.ca, H*RU:shaw.ca
X-HELO: smtp-out-so.shaw.ca
X-Authority-Analysis: v=2.2 cv=UeUhcOaN c=1 sm=1 tr=0 a=WqCeCkldcEjBO3QZneQsCg==:117 a=WqCeCkldcEjBO3QZneQsCg==:17 a=IkcTkHD0fZMA:10 a=Bn6qyvZqEgS8r-9RAJ4A:9 a=QEXdDO2ut3YA:10
Subject: Re: can't access /cygdrive/c/Windows/Sysnative ?
References: <20161221201600 DOT GA11116 AT ingber DOT com> <6d28035f-c6e0-9c02-eca8-7fbacfc55f3f AT SystematicSw DOT ab DOT ca>
To: cygwin AT cygwin DOT com
From: Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Message-ID: <279cffd0-6cf5-5745-c67c-d10d789836dc@SystematicSw.ab.ca>
Date: Thu, 22 Dec 2016 12:22:05 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <6d28035f-c6e0-9c02-eca8-7fbacfc55f3f@SystematicSw.ab.ca>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfDMvPu5GyQ+0Te0MHuwjo2OFby7T8pky6/5I7rks4seVLZWmJR0Gl9Y+fCYu7WGpU9rR/aSJFjOoy7JQjmnBJUiPn+S/Ol/0YjkhwQeJgUDDW2QgxU5f YiLi99pmjoMehXwqFOJp/UJLGCGYLJCx2cMyZHMmPf/j89A3v8PYDQoMLHRu33xrU6IZmr90YVcRvw==
X-IsSubscribed: yes

On 2016-12-22 11:39, Brian Inglis wrote:
> On 2016-12-21 13:16, Lester Ingber wrote:
>> So, I guess that I should have seen that the Windows 10 Ubuntu 
>> bash.exe is actually written as a 32 bit code (they didn't use the 
>> 64-bit code as on my other true Ubuntu x64 platform?) from the
>> PE32+ info?:
>> # ls -l bash.exe
>> -rwxr-x---+ 2 TrustedInstaller TrustedInstaller 70656 Oct 14 20:57 bash.exe
>> # file bash.exe
>> bash.exe: PE32+ executable (console) x86-64, for MS Windows
> 
> which is exactly the same as Cygwin 64 bash:
> 
> $ file /bin/bash /proc/cygdrive/c/WINDOWS/system32/bash
> /bin/bash:                              PE32+ executable (console) x86-64, for MS Windows
> /proc/cygdrive/c/WINDOWS/system32/bash: PE32+ executable (console) x86-64, for MS Windows

The PE32 format is to allow execution from or by 32 bit world; the 
+ hints it contains 64 bit code, as does the arch x86-64.

From Cygwin 32 the 64 bit WSL/UoW/BfW "bash" launcher is not visible 
as the 64 bit system directories are not in the PATH:

$ file `which -a bash`
/usr/bin/bash: PE32 executable (console) Intel 80386, for MS Windows

> as they are both Windows console exes: Windows "bash" is just the 
> launcher for the console in which WSL/UoW/BfW runs -- trust MS to 
> pick another wrong and confusing name to be "cute" -- like calling 
> mintty "bash".

...forgot to add WSL/UoW/BfW bash, which is yet another 64 bit 
executable in ELF not PE32/+ format:

$ file `which -a bash`
/bin/bash: ELF 64-bit LSB  executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=54967822da027467f21e65a1eac7576dec7dd821, stripped

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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