From: "Sean Quinlan" <sean@quadfish.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] vac merge semantics
Date: Tue, 20 Aug 2002 13:58:29 -0400 [thread overview]
Message-ID: <49191.212.83.187.183.1029866309.squirrel@www.quadfish.com> (raw)
In-Reply-To: <09174ed505404e969b0e40bc4ef95296@plan9.bell-labs.com>
All the info needed to get the qids right is available,
however vacfs does not yet have the code that uses this info.
I`ll fix this when I get back fro, vacation...
the idea is that each tree that is merged contains the
max qid - vac leaves the correct size hole in the qid`
space and info that vacfs is supposed to use to
offset the qids in the merged tree...
seanq
> The mount table works by using qid's. Start playing fast and loose and
> you can end up with some very strange name spaces.
next prev parent reply other threads:[~2002-08-20 17:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-20 0:50 presotto
2002-08-20 17:58 ` Sean Quinlan [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-21 18:31 Richard Miller
2002-08-19 22:15 Charles Forsyth
2002-08-19 19:37 Richard Miller
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=49191.212.83.187.183.1029866309.squirrel@www.quadfish.com \
--to=sean@quadfish.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).