From: "rob pike" <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9P to 9P2000 migration path
Date: Sun, 28 Jan 2001 14:23:48 -0500 [thread overview]
Message-ID: <20010128192407.7C8F3199EF@mail.cse.psu.edu> (raw)
> What is the migration strategy for 9P to 9P2000? Is
> there consideration given to operating a network in
> mixed mode (9P/9P2000) and what it would take to
> do so? Is there a provision for protocol versioning?
A great deal of agonizing and very little decisiveness went into
resolving this issue. The current situation is to have the physical
(main, worm-based) file servers honor both protocols, but to have the
CPU and terminal kernels talk only the new one (and of course
old ones talk only the old one). Thus both old and new
systems can coexist. We have a program that can be interposed into a
conversation to let a new kernel talk to an old service, but
translating client new protocol to server old protocol. This is
sufficient, for example, to let the new kernel boot from the existing
binary of disk/kfs. Over time, we will translate the applications to
use the new protocol only.
That sort of thing.
The necessary hooks for protocol versioning is provided by the
"version" message.
-rob
next reply other threads:[~2001-01-28 19:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-28 19:23 rob pike [this message]
2001-01-29 5:19 ` Dan Cross
-- strict thread matches above, loose matches on Subject: below --
2001-02-02 1:31 jmk
2001-02-05 18:29 ` Dan Cross
2001-01-27 21:58 [9fans] 9P2000 rob pike
2001-01-28 18:44 ` [9fans] 9P to 9P2000 migration path Fariborz 'Skip' Tavakkolian
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=20010128192407.7C8F3199EF@mail.cse.psu.edu \
--to=rob@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).