From: Jack Johnson <fragment@nas.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Summary of Plan9 for jargon file
Date: Wed, 5 Feb 2003 11:31:44 -0800 [thread overview]
Message-ID: <3E4166A0.8070305@nas.com> (raw)
In-Reply-To: <9bbb3d829d428c918d69fef9531a3444@plan9.bell-labs.com>
Russ Cox wrote:
> i think this is what you're talking about,
> but it hardly seems a fitting entry. also it's
> not true anymore, a fact i have recently
> discovered by crashing unix boxes with
> reasonable nfs traffic. good luck crashing
> plan 9 with 9p traffic.
That's hardly fair.
Which crashes first, Plan 9 with heavy NFS traffic or Unix with heavy 9p
traffic?
;)
-J
next prev parent reply other threads:[~2003-02-05 19:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 19:05 Joel Salomon
2003-02-05 19:11 ` andrey mirtchovski
2003-02-05 19:34 ` Skip Tavakkolian
2003-02-05 19:13 ` Russ Cox
2003-02-05 19:31 ` Jack Johnson [this message]
2003-02-07 6:50 ` Roman V. Shaposhnick
2003-02-07 12:20 C H Forsyth
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=3E4166A0.8070305@nas.com \
--to=fragment@nas.com \
--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).