From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <f8647f340b126db3c4e4904080140810@quanstro.net>
To: 9fans@9fans.net
From: erik quanstrom <quanstro@quanstro.net>
Date: Tue,  2 Dec 2008 13:18:35 -0500
In-Reply-To: <1228241551.7593.48.camel@goose.sun.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] How to implement a moral equivalent of automounter
Topicbox-Message-UUID: 5595fb6e-ead4-11e9-9d60-3106f5b1d025

> I totally agree that a shim filesystem whould solve an immediate issues
> perfectly. The solution, however, will be a 'black box'. If I mount
> such a filesystem under /n/ all I would see in my name space is a single
> mount. Everything that goes on underneath /n/<name>/stuff... will be
> completely hidden from me inside the namespace of the shim fileserver
> itself.

that's the point.

> I need to do in order to find out is:
>   $ mount | fgrep /set/tools/gcc/4.0/intel-S2
> and then I can manipulate my namespace even further to suit my needs.

since nfs is always directly mounted, i think you are confusing
direct mounts with things that are accessable because you have
mounted a server which has mounted something else.

i would think that either you want encapsulation or you don't.
see-through encapsulation would seem to me to be a contradiction
in terms.

if you don't, and you really need to know what's on the other
end, you should mount it yourself.  /lib/namespace is a big
help in this.

if you do, then you don't want to care what's over there.

- erik