From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] mounting channels in a Plan 9 server?
Date: Mon, 29 Mar 2004 21:23:26 +0100 [thread overview]
Message-ID: <7beb0bc1a3de01c3c6844789bf84f187@vitanuova.com> (raw)
In-Reply-To: <9b0916ab8db61cc99e267e7e550558a0@plan9.ucalgary.ca>
> trivially it could be done using general plan9 tools by mounting A
> somewhere, mounting B in one of the directories served by A and
> srvfs-ing the whole thing, but what if I don't want to post a file
> descriptor in /srv?
then use exportfs directly (it's what srvfs uses, after all).
this is the correct solution; in general you can't just add the
namespace for one 9p server into another - after all they use
different qid, tag and fid spaces.
this kind of multiplexing is exactly what exportfs is for. (along
with the kernel itself).
you could of course do the job of exportfs within your own fileserver
(but there are lots of non-trivial gotchas). in limited domains, this
can be a reasonable approach; i've done similar things in the past.
prev parent reply other threads:[~2004-03-29 20:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-27 17:38 andrey mirtchovski
2004-03-29 20:23 ` rog [this message]
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=7beb0bc1a3de01c3c6844789bf84f187@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).