From: lego12239@yandex.ru
To: "Claude Noël" <dogedoge61@gmail.com>
Cc: 9fans@9fans.net
Subject: Re: [OBORONA-SPAM] [9fans] Why is there no simple equivelent to plan9's pipes on linux?
Date: Mon, 28 Jun 2021 22:41:39 +0300 [thread overview]
Message-ID: <20210628194139.GA10869@legohost> (raw)
In-Reply-To: <746aac4a5f5464e4530d6a54b5b22555070cb9be.camel@gmail.com>
On Wed, Jun 16, 2021 at 12:02:54PM -0400, Claude Noël wrote:
> Plan 9 pipes:
> - can be opened by multiple proccesses
> - preserve write boundries
> - will cache a single write
> - 2 way
> - simple to use
>
> There's not really anything on linux that really compares to this.
May be. But what about unix domain sockets?
--
Олег Неманов (Oleg Nemanov)
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T127c618288a5cd57-M2d76c62a7ca7a87e8a96570e
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2021-06-28 19:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 16:02 Claude Noël
2021-06-28 18:59 ` jklowden
2021-06-28 19:41 ` lego12239 [this message]
2021-06-29 10:03 ` [OBORONA-SPAM] " Ethan Gardener
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=20210628194139.GA10869@legohost \
--to=lego12239@yandex.ru \
--cc=9fans@9fans.net \
--cc=dogedoge61@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).