From: Kenji Okamoto <okamoto@granite.cias.osakafu-u.ac.jp>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cpu command and 9660srv
Date: Thu, 27 May 2004 11:47:53 +0900 [thread overview]
Message-ID: <efbbe200f0bf3d2f06be0371c22a6275@granite.cias.osakafu-u.ac.jp> (raw)
In-Reply-To: <77cf02f49a01854b5a39833b8527ed27@granite.cias.osakafu-u.ac.jp>
> By the way, I forgot to mention that our new Plan 9 network
> works very fine for 5 terminals with no stress to use at a time.
> We use Venti+Fossil file server (1.6GHz Pen4, 1GB memory,
> and 120GB (for main) + 40GB (for other) IDE disks.
Oops!
120GB for venti only, and 40GB for fossil+cache+9fat+other.
Sorry.
Kenji
prev parent reply other threads:[~2004-05-27 2:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-21 7:21 Kenji Okamoto
2004-05-21 8:02 ` lucio
2004-05-21 8:11 ` Charles Forsyth
2004-05-21 8:43 ` Kenji Okamoto
2004-05-21 9:16 ` Kenji Okamoto
2004-05-21 9:41 ` Kenji Okamoto
2004-05-24 1:54 ` Kenji Okamoto
2004-05-27 2:47 ` Kenji Okamoto [this message]
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=efbbe200f0bf3d2f06be0371c22a6275@granite.cias.osakafu-u.ac.jp \
--to=okamoto@granite.cias.osakafu-u.ac.jp \
--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).