From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9P to 9P2000 migration path
Date: Thu, 1 Feb 2001 20:31:24 -0500 [thread overview]
Message-ID: <20010202013127.9CEED199D5@mail.cse.psu.edu> (raw)
On Mon Jan 29 00:20:33 EST 2001, cross@math.psu.edu wrote:
> In article <20010128192407.7C8F3199EF@mail.cse.psu.edu> you write:
> >That sort of thing.
> >
> >The necessary hooks for protocol versioning is provided by the
> >"version" message.
>
> I'm guessing it's easy for a file server to detect an old protocol
> client (Tversion won't be the first message sent from an old 9p client,
> as old 9p doesn't have Tversion. Any connection starting out this way
> won't be the new protocol).
>
> I was reading the file server paper again today while I was on the
> train, and one thing I noticed is that the disk-resident directory
> entry contains the 28 byte file name in a fixed width field. It would
> seem that if the restriction on file name length is being removed from
> the protocol, a similar change must be taking place in the file
> server. If this is the case, then the question becomes, ``how does one
> migrate data off of disk on an old file server and onto a new one?''
> Also, if the disk resident data structure is changing, is this a good
> time to move the length field to a vlong?
>
> - Dan C.
>
Yes, the disc-resident directory structure will change. I have a 4-step
or so plan on how to do this, of which I've implemented step 1 (I'm probably
in trouble because I haven't done any work on steps 2-4 for the past month).
The new structure will have a 64-bit length field.
I'd say more but some parts are still in flux.
--jim
next reply other threads:[~2001-02-02 1:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-02 1:31 jmk [this message]
2001-02-05 18:29 ` Dan Cross
-- strict thread matches above, loose matches on Subject: below --
2001-01-28 19:23 rob pike
2001-01-29 5:19 ` 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=20010202013127.9CEED199D5@mail.cse.psu.edu \
--to=jmk@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).