From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] sanity check
Date: Mon, 26 Sep 2005 18:16:32 +0100 [thread overview]
Message-ID: <23ca7e8f532ce9bce873c8591ebaed9a@vitanuova.com> (raw)
In-Reply-To: <97cf5bb32e4e73066bfbf1be4bcb8a49@quintile.net>
> What I have done is to modify 9fs such that if you do
> 9fs xxx and /srv/xxx exists then 9fs just mounts xxx.
this is the default for 9fs entries that are not explicitly
dealt with (as implemented by srv(4)).
> Thus if cifs is not running I can type 9fs dfs to connect to
> dfs in "this" window, and plumb 'Local 9fs dfs' to export it to
> all new windows. I usually close any idle windows and if there
> is one or two I want to keep I just do 9fs dfs again in those
> (and !9fs dfs in my sam window) to attach them.
>
> I just live with this behavior it just seems reasonable to me -
> but perhaps I am just used to it.
i use exportfs to provide an extra level of indirection
which gets around this awkwardness, providing a globally shared,
mutable namespace in /n.
i can plumb "Local 9fs dfs" and /n/dfs in all processes will contain
the newly acquired namespace. (actually i have a shell script,
named "local" which is this:
#!/bin/rc
plumb 'Local ' ^ $"*
[it's kind of ironic that it's named "local" when actually the desired
effect is a global one...]
thus in any window, i can do
local 9fs sources
and plumb files /n/sources to any other preexisting
window (for example page). i find this extremely convenient.
unlike nemo's volfs (which i haven't actually looked at, i'm afraid),
this doesn't do automatic fid rewrites when the underlying space is
changed, but it is implemented from existing parts in only 4 lines of shell script,
and imposes negligible overhead.
the DFS scheme suggested earlier could be easily implemented by using
a variation on this scheme.
next prev parent reply other threads:[~2005-09-26 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2005-09-26 17:21 ` Federico Benavento
2005-09-24 14:33 Fco. J. Ballesteros
2005-09-26 9:17 ` Steve Simon
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=23ca7e8f532ce9bce873c8591ebaed9a@vitanuova.com \
--to=rog@vitanuova.com \
--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).