From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] EOF on pipes?
Date: Mon, 26 Feb 2018 09:19:17 -0800 [thread overview]
Message-ID: <20180226171917.GL16114@mcvoy.com> (raw)
In-Reply-To: <20180226165802.sz5eklp6lfamzv2m@matica.foolinux.mooo.com>
What?!?! I put networking in some version of SCO, it most certainly
did have pipes. Maybe they were faked in the shell but I tend to think
I would have noticed that, I did all sorts of pipelines on that project.
So are you _sure_ the kernel doesn't implement pipes? SCO would have
to have taken them out, v7 has usr/sys/sys/pipe.c
On Mon, Feb 26, 2018 at 08:58:02AM -0800, Ian Zimmerman wrote:
> On 2018-02-26 23:03, Rudi Blom wrote:
>
> > From a piece of code I have in some SCO UNIX 3.2V4.2 source. SCO
> > doesn't have pipes, but you can simulate them.
>
> Is this a SCO speciality, or are there other UNIXes like that?
>
> Does it not even have pipe() in its libc?
>
> --
> Please don't Cc: me privately on mailing lists and Usenet,
> if you also post the followup to the list or newsgroup.
> To reply privately _only_ on Usenet and on broken lists
> which rewrite From, fetch the TXT record for no-use.mooo.com.
--
---
Larry McVoy lm at mcvoy.com http://www.mcvoy.com/lm
next prev parent reply other threads:[~2018-02-26 17:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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-25 13:07 Doug McIlroy
2018-02-25 13:16 ` George Michaelson
2018-02-25 13:56 ` arnold
2018-02-27 5:04 Rudi Blom
2018-02-27 5:48 ` Dave Horsfall
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=20180226171917.GL16114@mcvoy.com \
--to=lm@mcvoy.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).