From: Ken Brown <kbrown@cornell.edu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Cc: Stephen Provine <stephpr@microsoft.com>
Subject: Re: Future setup regression caused by 'mkdir: always check-for-existence' commit
Date: Mon, 26 Aug 2019 17:33:00 -0000 [thread overview]
Message-ID: <860a3bd2-fc37-27c0-54f3-0fce8add7c24@cornell.edu> (raw)
In-Reply-To: <MWHPR21MB08452B51987E8A239851F7BEB9A10@MWHPR21MB0845.namprd21.prod.outlook.com>
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 directory does not work any more. It used to be that "mkdir -m 755 /dev" would succeed, but now it returns a "File exists" error, after which attempts to create 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 this directory outside of the Cygwin environment before running the post-install steps.
>
> See https://github.com/git-for-windows/git/issues/2291#issuecomment-524433693 for 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://cygwin.com/ml/cygwin/2019-07/msg00152.html
This was a bug in a development snapshot, and it has already been fixed. You
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
b0c033bf3fae810b9e5a5c69f17bd4de63725691.
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
next prev parent reply other threads:[~2019-08-26 17:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 15:41 Stephen Provine via cygwin
2019-08-26 17:04 ` Eric Blake
2019-08-26 17:33 ` Ken Brown [this message]
2019-08-26 18:24 ` Stephen Provine via cygwin
2019-08-26 18:24 ` Ken Brown
[not found] ` <MWHPR21MB0845123AD4012BC4D100BE47B9A10@MWHPR21MB0845.namprd21.prod.outlook.com>
2019-08-27 12:51 ` Stephen Provine via cygwin
2019-08-27 17:54 ` Achim Gratz
2019-08-26 22:13 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=860a3bd2-fc37-27c0-54f3-0fce8add7c24@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
--cc=stephpr@microsoft.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).