From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: /dev/fd/N not synonymous with file descriptor N; it is on Linux
Date: Tue, 22 Jan 2019 09:25:00 -0000 [thread overview]
Message-ID: <151898514e462bd76cda8a227d4baa16@xs4all.nl> (raw)
In-Reply-To: <20190122090633.GK2802@calimero.vinschen.de>
On 2019-01-22 10:06, Corinna Vinschen wrote:
> On Jan 22 09:57, Houder wrote:
>> On 2019-01-22 09:50, Houder wrote:
>> > On Sun, 6 Jan 2019 21:19:50, Corinna Vinschen wrote:
>> > > This should work in the latest developer snapshot uploaded to
>> > > https://cygwin.com/snapshots/ Please give it a try.
>> > So, for the record only:
>>
>> and as another example, this STC succeeds on Linux ..., but fails on
>> Cygwin.
>>
>> 64-@@ ./stca /dev/fd/0 <<EOF
>> > bla
>> > EOF
>> fd1 = 0
>> argv[1] = /dev/fd/0
>> fd2 = 3
>> id = writefd2, errno = 13, errstr = Permission denied
>> 64-@@
>
> Not sure what you're testing. This is the result for me on both,
> Windows 8.1 and Windows 10 1809:
Curious! It fails (for me) on W7 ...
> Not sure what you're testing.
STC inherits a "read-only" open file descriptor from bash. On Linux
the file can be opened read-write (via procfs), because a new entry
is created in the open file table.
(opening the file read-write (via fdescfs) on FreeBSD would fail)
For this reason the output does not show what has been entered via
the here-doc.
In short, I was merely testing the semantics of Linux.
> )$ ./stca /dev/fd/0 <<EOF
> ? bla
> ? EOF
> fd1 = 0
> argv[1] = /dev/fd/0
> fd2 = 3
> buf = \
> Hello, world!
>
>
> Corinna
--
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-01-22 9:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-16 16:31 Houder
2018-12-16 20:28 ` Corinna Vinschen
2018-12-16 20:31 ` Corinna Vinschen
2018-12-16 21:36 ` Wayne Davison
2018-12-16 21:55 ` Corinna Vinschen
2018-12-17 4:30 ` Houder
2018-12-17 9:25 ` Corinna Vinschen
2018-12-17 11:26 ` Corinna Vinschen
2019-01-02 13:56 ` Houder
2018-12-17 3:41 ` Houder
2019-01-06 20:19 ` Corinna Vinschen
2019-01-22 8:50 ` Houder
2019-01-22 8:57 ` Houder
2019-01-22 9:06 ` Corinna Vinschen
2019-01-22 9:25 ` Houder [this message]
2019-01-22 9:42 ` Corinna Vinschen
2019-01-22 10:20 ` Houder
2019-01-22 10:39 ` Corinna Vinschen
2019-01-27 18:39 ` Houder
2019-01-27 21:57 ` Corinna Vinschen
2019-01-27 22:12 ` Corinna Vinschen
2019-01-28 14:15 ` Houder
2019-01-28 16:51 ` Corinna Vinschen
2019-01-22 9:02 ` Corinna Vinschen
2019-01-22 9:07 ` Corinna Vinschen
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=151898514e462bd76cda8a227d4baa16@xs4all.nl \
--to=houder@xs4all.nl \
--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).