From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 63759 invoked by alias); 15 Jun 2018 13:32:15 -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 63392 invoked by uid 89); 15 Jun 2018 13:32:14 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.2 spammy=HOME, dear, Tel, tel X-HELO: mga06.intel.com Received: from mga06.intel.com (HELO mga06.intel.com) (134.134.136.31) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 15 Jun 2018 13:32:13 +0000 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 15 Jun 2018 06:32:10 -0700 X-ExtLoop1: 1 Received: from irsmsx153.ger.corp.intel.com ([163.33.192.75]) by fmsmga007.fm.intel.com with ESMTP; 15 Jun 2018 06:32:09 -0700 Received: from irsmsx112.ger.corp.intel.com (10.108.20.5) by IRSMSX153.ger.corp.intel.com (163.33.192.75) with Microsoft SMTP Server (TLS) id 14.3.319.2; Fri, 15 Jun 2018 14:32:09 +0100 Received: from irsmsx102.ger.corp.intel.com ([169.254.2.146]) by irsmsx112.ger.corp.intel.com ([169.254.1.22]) with mapi id 14.03.0319.002; Fri, 15 Jun 2018 14:32:08 +0100 From: "Soegtrop, Michael" To: "cygwin@cygwin.com" Subject: RE: Unexpected behavior of ~ when calling bash from a different cygwin installation Date: Fri, 15 Jun 2018 14:49:00 -0000 Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A177880079D@IRSMSX102.ger.corp.intel.com> References: <0F7D3B1B3C4B894D824F5B822E3E5A1778800706@IRSMSX102.ger.corp.intel.com> In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A1778800706@IRSMSX102.ger.corp.intel.com> x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiY2Q1ODcxZWEtZTRmZS00OGQwLTg3MTUtNWNmZDBmNWJlMzg2IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiRHFIYkwyN1hwM0tnTE5VYW9UQmE1a1FMcUhWSllpM1pEbkFrYVNSWExRQ3lCc3FNUzlKT0l4M05rQ2hoN1dEMiJ9 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/msg00173.txt.bz2 Dear Cygwin Users, I got it, I just have to clear the HOME variable before. But I have a few more observations on this: the FAQ (section 4.20) state that the root path for the mount table depends= on the path of the cygwin1.dll, to which an executable is linked. This doe= sn't seem to be the case. E.g. when I do * start a bash via C:\bin\cygwinA\cygwin.bat=20 * cd to /cygdrive/c/bin/cygwinB/bin * ./bash The first and the second bash have both /=3DC:\bin\cygwinA although SysInte= rnals ProcExplorer clearly shows that the second bash loads the cygwin1.dll= from C:\bin\cygwinB and not from C:\bin\cygwinA. Is there some description= on how the path mapping really works? If I do: * start a bash via C:\bin\cygwinA\cygwin.bat=20 * cd to /cygdrive/c/bin/cygwinB/bin * /cygdrive/c/Windows/System32/cmd * bash The dlls to which the second bash links are the same in both cases, but in = the second case /=3D C:\bin\cygwinB in the second shell. And yes, I also read in section 4.20 of the FAQ that one shouldn't call one= Cygwin from another. But I think a clear handover from one bash to another= should work in a documented way. 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