From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 13 Jan 2012 18:58:01 +0100 From: tlaronde@polynum.com To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-ID: <20120113175801.GB1890@polynum.com> References: <20120113113026.GA419@polynum.com> <20120113133836.GA484@polynum.com> <20120113140834.GA849@polynum.com> <20120113160142.GA98@polynum.com> <20120113171734.77a40595@wks-ddc.exosec.local> <20120113164101.GB647@polynum.com> <4a3253f1f2669e02ba348dd33fe81688@coraid.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4a3253f1f2669e02ba348dd33fe81688@coraid.com> User-Agent: Mutt/1.4.2.3i Subject: Re: [9fans] fossil pb: FOUND! Topicbox-Message-UUID: 5ad01382-ead7-11e9-9d60-3106f5b1d025 On Fri, Jan 13, 2012 at 12:37:17PM -0500, erik quanstrom wrote: >[...] > each file server has a unique path name, called the qid (as charles > mentioned). but between (instances of) file servers, qids are not unique. But a "fully qualified qid", I mean, at this very moment, for the kernel, a resource is some qid served by some server. So (srv,qid) is an uniq identifier, even if only in a local context. We are a lot to call ourselves: "I" or "me". But in the context, this is an uniq identifier (because all other mees are not me!). For this, IP has found an elegant solution. There are identifiers that are only local. As long as there is no interconnexion, the identifiers are not absolutely uniq, but relatively uniq. And this is sufficient. But I realize that the problem is hard. And that all in all, the correct information is available from the file servers, and that when the namespace is concerned, we have all access potentially to huge resources; so by the nature of interconnexions, the answer is fuzzy. I will not exchange the distributed nature of Plan9; and the namespace; and the everything is a file etc. against the ability to have du(1) telling me "acurately" what is stored here and only here (since I have other means to know with the console). But this was obviously not clear for me till now! -- Thierry Laronde http://www.kergis.com/ Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C