From: Skip Tavakkolian <skipt@real.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fileserver problems
Date: Tue, 20 Jun 2000 00:37:03 -0700 [thread overview]
Message-ID: <3.0.5.32.20000620003703.00937aa0@mail.real.com> (raw)
In-Reply-To: <002601bfda83$1233d160$6f64a8c0@blue>
This would be quite a change from debugging at 300bps! (according to legend)
P.S. As enticement for a Seattle stop, I'd throw in a day of
flying around the Puget Sound in a 172. (I can just see
an ebay-esque bidding frenzy starting)
At 07:45 AM 6/20/00 +0100, Nigel Roles wrote:
>That would presumably be 24/7 service as well - he might turn up any time?
>
>----- Original Message -----
>From: "rob pike" <rob@plan9.bell-labs.com>
>To: <9fans@cse.psu.edu>
>Sent: Monday, June 19, 2000 9:08 PM
>Subject: Re: [9fans] fileserver problems
>
>
>> I've been through the code for the fileserver many times, but I can't seem
>> to figure out why this is happening. Any ideas would be really
>> appreciated.
>>
>> Give us your address and we'll send Ken out to fix it. That's our
>technique.
>>
>> -rob
>>
>
>
next prev parent reply other threads:[~2000-06-20 7:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-19 20:08 rob pike
2000-06-20 6:45 ` Nigel Roles
2000-06-20 7:37 ` Skip Tavakkolian [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-19 13:02 sah
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=3.0.5.32.20000620003703.00937aa0@mail.real.com \
--to=skipt@real.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).