From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 113132 invoked by alias); 26 Aug 2019 17:33:20 -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 113125 invoked by uid 89); 26 Aug 2019 17:33:19 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-6.7 required=5.0 tests=BAYES_00,GIT_PATCH_2,KAM_LOTSOFHASH,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS autolearn=ham version=3.3.1 spammy=brown, Brown, 0755 X-HELO: NAM01-BY2-obe.outbound.protection.outlook.com Received: from mail-eopbgr810130.outbound.protection.outlook.com (HELO NAM01-BY2-obe.outbound.protection.outlook.com) (40.107.81.130) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 26 Aug 2019 17:33:18 +0000 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Fe/Aeb7Caow0SpP8eF2amjO0W9dofEm6wDGIXBZC4zXR6WQcosIHtr9VVssSK0bezjz3foSrNxjyuFaVwndSBcPgh6OAlx7gvk7kY+kD2xH8JEZ525PfFHDgh4LCc0exAa8kyAi4IrSTQJdsWvkPd6egF7rLtuL2Cai8wEpoO1wI1Sw1FzvETDX63D/p5hwMve13u7aMkqqebt1l6fo80dszg0Gyb66qkMyvCNzMJ47V7mW/0YqkPDzW+GaOLoIo+Ax07Yfh22uUtrHH5d6TUaRpspqVVU9izdzP39BdBXVLRfooK5x27WKhBIDWCEUsZV3YmXu12yIEQPYNt1gEyA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=NRVekl5PKJU/6W3engbDx3/t7/1AVT+Ho403kVommFY=; b=KZQJcxwIdRDSxvMbI6A8h5FuFrPUOxunETMwDJee+XYfThUPkQ1ET3tFfiUDNijPCSRB2zQ3W0/s3/EzIgp8H8yAQVeZI/xlxAOTozLBp5s29dulm0uHxxgaAms3/RwCLAxn7ev3+jMEab9yt2blK16piPGTDQ8ZNIBj/6SXG1Vr5VzBx2JFIJLXEe7f68h69Z/lR+tf31cCpc2xNQLmm8oHudT74/RA6Bw0QDDIytqIQgldJ0T+LEQaoSJQRAE1bqsRTke327nR1kgM8U0l56zMlJIqY2kRAqa3CloBMtxSFQQSms5r67EnjzOumksR1LyjXAWnxr3eQD66yEP7Xw== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=NRVekl5PKJU/6W3engbDx3/t7/1AVT+Ho403kVommFY=; b=lG51y5NOd8hu4KYDdkDu66n8OzmA+cdY2fDJhP8V6fRK7eFmymz7lNcfcVIGFBFSwfqwTIfWWZBntl7ITxjrOhks7xRTrdOy56qaCUw0CqM2IL0Jo/lbBMeR0UsjmEtUDzOkCq3BrMhHgcvMl2KQovNEzaltmBo+s74UNgRpWqM= Received: from MWHPR21MB0845.namprd21.prod.outlook.com (10.173.51.139) by MWHPR21MB0173.namprd21.prod.outlook.com (10.173.52.19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2241.3; Mon, 26 Aug 2019 17:33:15 +0000 Received: from MWHPR21MB0845.namprd21.prod.outlook.com ([fe80::3085:a037:7cbc:be5]) by MWHPR21MB0845.namprd21.prod.outlook.com ([fe80::3085:a037:7cbc:be5%5]) with mapi id 15.20.2241.000; Mon, 26 Aug 2019 17:33:15 +0000 From: "Stephen Provine via cygwin" Reply-To: Stephen Provine To: Ken Brown , "cygwin@cygwin.com" Subject: RE: Future setup regression caused by 'mkdir: always check-for-existence' commit Date: Mon, 26 Aug 2019 18:24:00 -0000 Message-ID: References: <860a3bd2-fc37-27c0-54f3-0fce8add7c24@cornell.edu> In-Reply-To: <860a3bd2-fc37-27c0-54f3-0fce8add7c24@cornell.edu> authentication-results: spf=none (sender IP is ) smtp.mailfrom=stephpr@microsoft.com; x-ms-exchange-purlcount: 2 x-ms-oob-tlc-oobclassifiers: OLM:9508; received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-ms-exchange-transport-forked: True Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: 3Cqrtp6ZW0vwmJZN/fasFvpqWk6mRlj+g71MQM9J+bmE4kWeYe5PnEGXkcom/bTFOI5GizlLB71X3bFG7Ar6dQ== X-SW-Source: 2019-08/txt/msg00331.txt.bz2 It's possible that this issue contributes to the problem, but the fact that= you can manually create the "dev" directory outside of Cygwin (just mkdir = from Windows command prompt) to fix the problem tells me otherwise. If I un= derstand the logic change in commit b0c033bf3fae810b9e5a5c69f17bd4de6372569= 1, it would indicate to me that "mkdir 0755 /dev" in a post-install bash sc= ript (regardless of which one) would no longer work when it previously work= ed. This ultimately means that the /dev/fd directory does not exist and tha= t files like /dev/fd/63 cannot be created (the underlying error is "Filesys= tem is read-only", because the "dev" directory doesn't actually exist excep= t in Cygwin). It's quite possible that if /dev/fd/63 can be created that th= ere are some subsequent FIFO issues, but in this case the file can't even b= e created in the first place. I'd be happy to try the test release for cygwin-3.1.0, but I don't know how= to find it. Can you provide a link? Thanks, Stephen -----Original Message----- From: Ken Brown =20 Sent: Monday, August 26, 2019 10:04 AM To: cygwin@cygwin.com Cc: Stephen Provine Subject: Re: Future setup regression caused by 'mkdir: always check-for-exi= stence' commit On 8/26/2019 11:25 AM, Stephen Provine via cygwin wrote: > After this change (commit b0c033bf3fae810b9e5a5c69f17bd4de63725691), the = Git for Windows setup (and future Cygwin setups) do not correctly configure= bash features because the post-install step for configuring the /dev direc= tory does not work any more. It used to be that "mkdir -m 755 /dev" would s= ucceed, but now it returns a "File exists" error, after which attempts to c= reate the 'shm' and 'mqueue' directories fail and the /dev/fd, /dev/std{in,= out,err} links are not created. This causes some bash features to not work.= The fix (validated on Git for Windows) would be for setups to pre-create t= his directory outside of the Cygwin environment before running the post-ins= tall steps. >=20 > See https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fg= ithub.com%2Fgit-for-windows%2Fgit%2Fissues%2F2291%23issuecomment-524433693&= amp;data=3D02%7C01%7Cstephpr%40microsoft.com%7C227fabc69f4e434ae12a08d72a47= 63d2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637024358495313120&sd= ata=3D16rboEMc6kGEAzIWDGTjjg%2FVLeuguIbBh%2F9cJMl0oZI%3D&reserved=3D0 f= or the in-depth analysis. Note, this is not a current issue in Cygwin, but = is believed to become a FUTURE issue with the next release. It looks like you've bumped into the bug reported here: https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fcygw= in.com%2Fml%2Fcygwin%2F2019-07%2Fmsg00152.html&data=3D02%7C01%7Cstephpr= %40microsoft.com%7C227fabc69f4e434ae12a08d72a4763d2%7C72f988bf86f141af91ab2= d7cd011db47%7C1%7C0%7C637024358495313120&sdata=3DUa%2BocDgveO3LqqSP0Snz= emAihSysyV3jvae5WMxVA1M%3D&reserved=3D0 This was a bug in a development snapshot, and it has already been fixed. Y= ou should try the test release for cygwin-3.1.0 to confirm this. I don't think this problem has anything to do with commit b0c033bf3fae810b9= e5a5c69f17bd4de63725691. Ken -- 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