From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: From: "Fco. J. Ballesteros" Date: Sat, 24 Sep 2005 16:33:29 +0200 To: 9fans@cse.psu.edu Subject: Re: [9fans] sanity check MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: 911249a8-ead0-11e9-9d60-3106f5b1d025 : If you create a rio window and then you change : the name space sitting under rio, the existing window's : name space (which has already been copied from rio) : doesn't inherit the new path. So just re-binding things : doesn't work as you might hope. I'm not sure I understood correctly what you are trying to do, but regarding re-binding things, it can be done by using volfs (the port of Plan B volumes to Plan 9), there's a working version that is a a little bit slow, and I'm finishing now a more efficient version. You'll have to wait a week or two to get a reliable veersion of the program. The way to do it with volfs would be just to echo $sysname #s/srvforcifs /cifs >/dev/vols to declare your new volume named "/cifs", reacheable via 9P at #s/srvforcifs. and then mount -c /srv/vols /n/cifs /cifs before starting rio, to get at /n/cifs whatever file server is known as /cifs. Volfs takes care of rewriting fids to match the new files found when it switches from one file tree to another. This means that you don't have to worry to update your binds. If you want to start a new tree, you can rearrange your internal name space and restart. /n/cifs would appear to be empty until you start your program. When it becomes available, you'll get it in /n/cifs. If you kill your program and start a new one, that one would be mounted instead. hth