From: "Fco. J. Ballesteros" <nemo@lsub.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] sanity check
Date: Sat, 24 Sep 2005 16:33:29 +0200 [thread overview]
Message-ID: <f97307292fece7f6b71e62d1e248d3e1@lsub.org> (raw)
: 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
next reply other threads:[~2005-09-24 14:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-24 14:33 Fco. J. Ballesteros [this message]
2005-09-26 9:17 ` Steve Simon
-- strict thread matches above, loose matches on Subject: below --
2005-09-24 10:22 Steve Simon
2005-09-24 11:28 ` Russ Cox
2005-09-25 3:47 ` Dave Eckhardt
2005-09-26 9:07 ` Steve Simon
2005-09-26 17:16 ` rog
2005-09-26 17:21 ` Federico Benavento
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f97307292fece7f6b71e62d1e248d3e1@lsub.org \
--to=nemo@lsub.org \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).