From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Streaming 9P is out
Date: Sat, 8 Jan 2011 20:05:33 -0500 [thread overview]
Message-ID: <56e84e4da0c51aa763f72a62670de813@plug.quanstro.net> (raw)
In-Reply-To: <AANLkTi=y4W7OdBSOxBnmnfuE4FOYr4NUv7n2dEXiAJgS@mail.gmail.com>
> This ought to work, but I wanted to establish a difference between
> regular fds, which you can read and write and seek and all that
> goodness, and streams, which are for reading OR writing sequentially.
i'm not sure why one would want this. there are already fds on
which must be read or written sequentially. they're called pipes.
- erik
next prev parent reply other threads:[~2011-01-09 1:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-08 7:24 John Floren
2011-01-08 10:45 ` Seed
2011-01-08 13:11 ` Bruce Ellis
2011-01-08 15:16 ` David Leimbach
2011-01-09 0:31 ` cinap_lenrek
2011-01-09 0:46 ` John Floren
2011-01-09 1:05 ` erik quanstrom [this message]
2011-01-09 1:53 ` cinap_lenrek
2011-01-09 2:24 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-01-09 2:42 ` ron minnich
2011-01-09 1:58 ` cinap_lenrek
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=56e84e4da0c51aa763f72a62670de813@plug.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).