From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9P to 9P2000 migration path
Date: Mon, 5 Feb 2001 13:29:35 -0500 [thread overview]
Message-ID: <200102051829.NAA18685@augusta.math.psu.edu> (raw)
In-Reply-To: <20010202013127.9CEED199D5@mail.cse.psu.edu>
In article <20010202013127.9CEED199D5@mail.cse.psu.edu> you write:
>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.
If this is the case, then one suggestion is to reserve 32 bits after
each timestamp on disk. Then, should it ever come to pass that times
change to 64 bit integers, one needn't change the layout of data on
disk except to start using those 32 bits....
- Dan C.
next prev parent reply other threads:[~2001-02-05 18:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-02 1:31 jmk
2001-02-05 18:29 ` Dan Cross [this message]
-- 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=200102051829.NAA18685@augusta.math.psu.edu \
--to=cross@math.psu.edu \
--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).