From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH 0/2] Provide virtual /dev/fd and /dev/{stdin, stdout, stderr} symlinks
Date: Fri, 25 Feb 2022 16:46:35 +0100 (CET) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.2202251645090.11118@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <YhTYazKXC+2X2TbU@calimero.vinschen.de>
Hi Corinna,
On Tue, 22 Feb 2022, Corinna Vinschen wrote:
> On Feb 21 14:36, Johannes Schindelin wrote:
> > These symbolic links are crucial e.g. to support process substitution (Bash's
> > very nice `<(SOME-COMMAND)` feature).
> >
> > For various reasons, it is a bit cumbersome (or impossible) to generate these
> > symbolic links in all circumstances where Git for Windows wants to use its
> > close fork of the Cygwin runtime.
> >
> > Therefore, let's just handle these symbolic links as implicit, virtual ones.
> >
> > If there is appetite for it, I wonder whether we should do something similar
> > for `/dev/shm` and `/dev/mqueue`? Are these even still used in Cygwin?
>
> "still used"? These are the dirs to store POSIX semaphors, message
> queues and shared mem objects.
Okay. I guess we do not really use them in Git for Windows ;-)
> These have to be real on-disk dirs.
Could I ask you to help me understand why? Do they have to be writable? Or
do the things that are written into them have to be persisted between
Cygwin sessions?
I ask because it would be really helpful for Git for Windows if we could
get away with _not_ having those directories.
> > Johannes Schindelin (2):
> > Implicitly support the /dev/fd symlink and friends
> > Regenerate devices.cc
> >
> > winsup/cygwin/Makefile.am | 1 +
> > winsup/cygwin/devices.cc | 1494 ++++++++++++++++--------------
> > winsup/cygwin/devices.h | 3 +-
> > winsup/cygwin/devices.in | 4 +
> > winsup/cygwin/dtable.cc | 3 +
> > winsup/cygwin/fhandler.h | 28 +
> > winsup/cygwin/fhandler_dev_fd.cc | 53 ++
> > 7 files changed, 879 insertions(+), 707 deletions(-)
> > create mode 100644 winsup/cygwin/fhandler_dev_fd.cc
>
> Pushed.
Thank you!
Dscho
next prev parent reply other threads:[~2022-02-25 15:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 13:36 [PATCH 0/2] Provide virtual /dev/fd and /dev/{stdin,stdout,stderr} symlinks Johannes Schindelin
2022-02-21 13:36 ` [PATCH 1/2] Implicitly support the /dev/fd symlink and friends Johannes Schindelin
2022-02-21 13:36 ` [PATCH 2/2] Regenerate devices.cc Johannes Schindelin
2022-02-22 12:34 ` [PATCH 0/2] Provide virtual /dev/fd and /dev/{stdin,stdout,stderr} symlinks Corinna Vinschen
2022-02-25 15:46 ` Johannes Schindelin [this message]
2022-02-28 9:24 ` [PATCH 0/2] Provide virtual /dev/fd and /dev/{stdin, stdout, stderr} symlinks Corinna Vinschen
2022-02-28 9:57 ` Corinna Vinschen
2023-03-28 8:34 ` Johannes Schindelin
2022-02-25 18:35 ` [PATCH 0/2] Provide virtual /dev/fd and /dev/{stdin,stdout,stderr} symlinks Brian Inglis
2023-03-28 8:36 ` Johannes Schindelin
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=nycvar.QRO.7.76.6.2202251645090.11118@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=cygwin-patches@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).