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=O2PEScnFBVGTKqWJ QDtqk0fGqdHfKKs1uOfqIS+naCZJqXQWAKdODShOFnKwM4oojcEFPaenDX1CbFEl ATtuUeAaDjHqLANdcBUtghfmWcwUBc1/SQbNGyrBaATCEynpXRLZ05L+n0eFqDuV HmkDQiLWRS5I7k0ZROggSk6Oke0= 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=++SQ4B0o/rfWZAxQmVuGBc stBck=; b=lk18VtAPI6lEDAq24Eq2aKnfi5Qex1hJ/HgmnVExM+B5RQBEqkcBd5 MESRtMRb+I6fJSHUrkNMFR28zWQ1U6OW1FCZuIBlB1cBCEES3BOXLGbEZT8R+but SQE7OXB0tessQyBRzuUZXFz9TBpdW/2qAztCkqmZv+U+X8K7pllwo= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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, H*RU:sk:smtp-ou, Hx-spam-relays-external:shaw.ca, H*r: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=xr3FLztcjJC4yfa9wNUA:9 a=QEXdDO2ut3YA:10 Subject: Re: can't access /cygdrive/c/Windows/Sysnative ? References: <20161221201600 DOT GA11116 AT ingber DOT com> To: cygwin AT cygwin DOT com From: Brian Inglis Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca Message-ID: <6d28035f-c6e0-9c02-eca8-7fbacfc55f3f@SystematicSw.ab.ca> Date: Thu, 22 Dec 2016 11:39:31 -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: <20161221201600.GA11116@ingber.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfNeYw9SWfoJUi18JH+h0wRYbQopXqKCT3iSWbJ6Kjm4SdayiUfOc/5L6J5Dqbw6lrL4AJMWbpdEQSpy7BDhXuMkyTJu1tgsbBcsXuEGr83AmJVTNvkwW u0L/GbgTh/JUe/2gAHM+DAtGoG0oBbq4ECaBsElHQE/00G36bNNfIVFPjOGZmF/xBMRkeTo5aIrgtw== X-IsSubscribed: yes 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 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". -- 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