From: Steve Harris <scharris@worldnet.att.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] pipefile
Date: Sun, 30 Jul 2000 18:46:14 -0500 [thread overview]
Message-ID: <20000730184614.A1429@tiger.home.net> (raw)
On Sun, 30 Jul 2000 18:17:32 rob pike wrote:
> Here's a version that doesn't implicitly assume /dev/cons.
If you don't mind, could you also say a word as to what made the
/dev/cons case special? Who was writing to /dev/cons all of the
keyboard input so that it worked? (rio?)
next reply other threads:[~2000-07-30 23:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-30 23:46 Steve Harris [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-08-03 23:46 okamoto
2000-08-03 4:49 rob pike
2000-08-03 4:15 okamoto
2000-08-03 3:44 okamoto
2000-08-03 7:14 ` Matt
2000-08-03 3:19 okamoto
2000-08-03 0:19 okamoto
2000-08-02 21:19 rob pike
[not found] <rob@plan9.bell-labs.com>
2000-08-02 14:48 ` rob pike
2000-08-02 15:49 ` James A. Robinson
2000-08-02 7:55 okamoto
2000-08-03 8:21 ` Boyd Roberts
2000-07-31 9:47 okamoto
2000-07-31 4:55 rob pike
2000-07-31 4:40 okamoto
2000-07-31 1:14 rob pike
2000-08-02 3:40 ` Skip Tavakkolian
2000-08-03 1:21 ` Skip Tavakkolian
2000-07-30 23:17 rob pike
2000-07-30 23:06 rob pike
2000-07-30 22:38 Steve Harris
2000-07-30 19:54 rob pike
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=20000730184614.A1429@tiger.home.net \
--to=scharris@worldnet.att.net \
--cc=9fans@cse.psu.edu \
/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).