From: Cedric Blancher <cedric.blancher@gmail.com>
To: cygwin@cygwin.com
Subject: Re: process substitution to create a virtual file doesn't work in chroot environment
Date: Mon, 28 Aug 2023 07:13:00 +0200 [thread overview]
Message-ID: <CALXu0UfmE1fAM+ibPjbH8fXDhKyCePOWAmW_PxLeVjb0wKPVsw@mail.gmail.com> (raw)
In-Reply-To: <CAEF1h+XMtnd0_28cLNnEB2Q+XAxXE3VMZtXh9LLQzeP7n-fAJw@mail.gmail.com>
On Mon, 28 Aug 2023 at 00:14, Cary Lewis via Cygwin <cygwin@cygwin.com> wrote:
>
> In a cygwin process that is started either from mintty or bash directly the
> following:
>
> $ user=234
>
> $ ./cat <(echo $user)
> 234
> works as expected.
>
> But after a chroot:
>
> $ chroot . ./bash
> user=234
> $ ./cat <(echo $user)
> ./cat: /dev/fd/63: No such file or directory
>
> In the directory I am chrooting in, I created a tmp folder, as well as
> proc, proc/self, and proc/self/fd, and a dev directory.
Can you strace -f the bash process to see what happens? How does ls -l
/dev/ look like?
Ced
--
Cedric Blancher <cedric.blancher@gmail.com>
[https://plus.google.com/u/0/+CedricBlancher/]
Institute Pasteur
next prev parent reply other threads:[~2023-08-28 5:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-27 22:13 Cary Lewis
2023-08-28 5:13 ` Cedric Blancher [this message]
2023-08-28 8:50 ` Corinna Vinschen
2023-10-21 22:41 ` Cygwin |chroot()| "bad" - but what should replace it ? / was: " Roland Mainz
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=CALXu0UfmE1fAM+ibPjbH8fXDhKyCePOWAmW_PxLeVjb0wKPVsw@mail.gmail.com \
--to=cedric.blancher@gmail.com \
--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).