From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <49191.212.83.187.183.1029866309.squirrel@www.quadfish.com> Subject: Re: [9fans] vac merge semantics From: "Sean Quinlan" To: <9fans@cse.psu.edu> In-Reply-To: <09174ed505404e969b0e40bc4ef95296@plan9.bell-labs.com> References: <09174ed505404e969b0e40bc4ef95296@plan9.bell-labs.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Date: Tue, 20 Aug 2002 13:58:29 -0400 Topicbox-Message-UUID: def12b36-eaca-11e9-9e20-41e7f4b1d025 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.