From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <dd6fe68a0812061506u594b269fp1fbf930b93aba564@mail.gmail.com>
Date: Sat,  6 Dec 2008 15:06:25 -0800
From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] Explanation of binding from ftpfs
In-Reply-To: <cca2e5880812061452l5e9943dv344ba471bd7f668d@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <cca2e5880812061244m4ea907e5v81b8c4ca2c397b75@mail.gmail.com>
	 <cca2e5880812061417j4265bad7g9bf960742c80ad62@mail.gmail.com>
	 <cca2e5880812061452l5e9943dv344ba471bd7f668d@mail.gmail.com>
Topicbox-Message-UUID: 5c33b25e-ead4-11e9-9d60-3106f5b1d025

ns is showing you the best name it has
for the resource in question.  if you did
bind /n/ftp/dir /n/tmp,
then it can't tell you that you did
mount '#s/ftp' /n/tmp
because that's not accurate--'#s/ftp' would
get you /n/ftp, not /n/ftp/dir.

so it shows you /n/ftp/dir, because that
is the name that was used at the time,
even if that name no longer means
the same thing.

russ