From: rudi.j.blom@gmail.com (Rudi Blom)
Subject: [TUHS] EOF on pipes?
Date: Tue, 27 Feb 2018 12:04:46 +0700 [thread overview]
Message-ID: <CAMYpm87ugxnUne3pwxhdt3YYiLP+i5FgqyQytHoVKgKizuVW+w@mail.gmail.com> (raw)
pipes in SCO UNIX 3.2V4.2,
It's long, long ago, so excuses for vagueness. I think the issue was
not pipe() perse, but the difference in functionality between 'pipe
filesystem' and streams pipes.
By using pipe() you create a FIFO pipe with certain limitations
(including 5120 write limit). When you open the streams device twice
and ioctl() two file descriptors together you have more flexibility.
Excuses for the possible confusion.
next reply other threads:[~2018-02-27 5:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 5:04 Rudi Blom [this message]
2018-02-27 5:48 ` Dave Horsfall
-- strict thread matches above, loose matches on Subject: below --
2018-02-25 13:07 Doug McIlroy
2018-02-25 13:16 ` George Michaelson
2018-02-25 13:56 ` arnold
2018-02-25 0:53 Norman Wilson
2018-02-25 16:29 ` Paul Winalski
2018-02-25 22:25 ` Lyndon Nerenberg
2018-02-25 23:18 ` Bakul Shah
2018-02-26 2:39 ` Grant Taylor
2018-02-24 21:33 Dave Horsfall
2018-02-24 23:13 ` Ron Natalie
2018-02-24 23:42 ` Bakul Shah
2018-02-24 23:46 ` Nelson H. F. Beebe
2018-02-24 23:46 ` Jon Steinhart
2018-02-26 16:03 ` Rudi Blom
2018-02-26 16:58 ` Ian Zimmerman
2018-02-26 17:19 ` Larry McVoy
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=CAMYpm87ugxnUne3pwxhdt3YYiLP+i5FgqyQytHoVKgKizuVW+w@mail.gmail.com \
--to=rudi.j.blom@gmail.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 NNTP newsgroup(s).