public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Future setup regression caused by 'mkdir: always check-for-existence' commit
Date: Mon, 26 Aug 2019 22:13:00 -0000	[thread overview]
Message-ID: <87o90b4wfb.fsf@Rainer.invalid> (raw)
In-Reply-To: <MWHPR21MB08452B51987E8A239851F7BEB9A10@MWHPR21MB0845.namprd21.prod.outlook.com>	(Stephen Provine via cygwin's message of "Mon, 26 Aug 2019 15:25:43	+0000")

Stephen Provine via cygwin writes:
> 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.

Cygwin does not create these directories in postinstall nor does any
package provide them, setup.exe does.  So you can assume the existence
of these directories in Cygwin.

https://cygwin.com/cygwin-ug-net/using-specialnames.html

The /dev/std* links are created by bash postinstall and doing that still
works (and the link shows up in the backing filesystem, not just the
virtual one).

> 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.

It seems mkdir gets spooked by the overlay of the virtual /dev over the
real one.  That's clearly a bug that needs fixing, IMHO.
You can work around by using a different path to the same directory (via
/proc/cygdrive, say).

> 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.

You can test that assumption by doing a fresh install of the current test version of Cygwin
3.1.0, but based on what I see on a system that has been updated to this
version I'd think Cygwin would not trigger this bug.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

--
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

      parent reply	other threads:[~2019-08-26 18:24 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
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 [this message]

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=87o90b4wfb.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=cygwin@cygwin.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).