From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 56468 invoked by alias); 16 Jun 2018 08:14:19 -0000 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 Received: (qmail 54827 invoked by uid 89); 16 Jun 2018 08:11:33 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=preferably, dear, states, Tel X-HELO: mga14.intel.com Received: from mga14.intel.com (HELO mga14.intel.com) (192.55.52.115) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 16 Jun 2018 08:11:32 +0000 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Jun 2018 01:11:30 -0700 X-ExtLoop1: 1 Received: from irsmsx107.ger.corp.intel.com ([163.33.3.99]) by fmsmga005.fm.intel.com with ESMTP; 16 Jun 2018 01:11:30 -0700 Received: from irsmsx102.ger.corp.intel.com ([169.254.2.146]) by IRSMSX107.ger.corp.intel.com ([169.254.10.238]) with mapi id 14.03.0319.002; Sat, 16 Jun 2018 09:11:29 +0100 From: "Soegtrop, Michael" To: "cygwin@cygwin.com" Subject: RE: Unexpected behavior of ~ when calling bash from a different cygwin installation Date: Sat, 16 Jun 2018 11:13:00 -0000 Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A17788010BF@IRSMSX102.ger.corp.intel.com> References: <0F7D3B1B3C4B894D824F5B822E3E5A1778800706@IRSMSX102.ger.corp.intel.com> <0F7D3B1B3C4B894D824F5B822E3E5A177880079D@IRSMSX102.ger.corp.intel.com> <1307619899.20180616023803@yandex.ru> In-Reply-To: <1307619899.20180616023803@yandex.ru> x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYzgyMGM5ZGYtNmVjNi00NjU1LWFlZmQtM2E5MDI4ZTZlMmQ5IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiZGlHNlhsU24rakFHNDhRdExzVUthY2dCQ0lRemZkTHZpR2xVUlpRUDJZeklpWmJnc3BscW5CSjU1anZmZmV2cSJ9 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2018-06/txt/msg00188.txt.bz2 Dear Andrey, > The mapping is consistent throughout the execution tree. I would like to understand the underlying mechanism. The documentation (FAQ= section 4.20) states (as far as I understand) that the Windows path of the= Cygwin system root an executable sees is the parent directory of the folde= r in which the cygwin1.dll resides which is loaded by an executable. As I s= howed, this doesn't seem to be the case. How does it work then? How is the = system root folder passed from parent to child? > At best, nothing will work Actually if I put cmd in between and clear a few environment variables it w= orks very well in fairly complicated scenarios. Still I would like to under= stand how the underlying mechanisms work (preferably without reverse engine= ering). Best regards, Michael Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Christian Lamprechter Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -- 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