From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cpu commans to v3 server
Date: Sun, 5 May 2002 01:48:28 -0400 [thread overview]
Message-ID: <453426bf2fdb8d01363ff05c83a2b7fc@plan9.bell-labs.com> (raw)
Cpu won't work to v3 cpu servers. Sorry.
The other way around works -- cpu from v3 to v4.
The problem is that there's no equivalent of
srvold9p in the other direction. Even once you
get cpu to negotiate correctly, exportfs starts
speaking 9P2000 to the old system, which confuses
things enough that the remote system hangs up.
Russ
next reply other threads:[~2002-05-05 5:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-05 5:48 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-05 1:16 Russ Cox
2002-05-05 1:20 ` Christopher Nielsen
2002-05-04 23:07 Russ Cox
2002-05-04 23:32 ` arisawa
2002-05-04 22:14 Russ Cox
2002-05-04 21:56 ` arisawa
2002-05-04 21:03 arisawa
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=453426bf2fdb8d01363ff05c83a2b7fc@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).