From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] interaction of net.alt and factotum
Date: Tue, 14 Dec 2010 13:19:53 -0500 [thread overview]
Message-ID: <8f2874e1e9314a2a2af78a99b287b018@coraid.com> (raw)
In-Reply-To: <20101214180515.GK19600@gradx.cs.jhu.edu>
> On Tue, Dec 14, 2010 at 01:00:33PM +0000, Steve Simon wrote:
> > Is there a way to hook into the napespace of factotum (I beleive there was a kernel
> > patch to make /proc/??/ns writable which should do it but I was hoping for a solution
> > that just used "a clever plan9 trick"
>
> I needed read access to this namespace and so bound an exportfs in /srv as
> one of the last lines of cpurc. You could spawn an agent which was prepared
> to receive, over a /srv pipe, the name of a /srv pipe and mount it over
> /net.alt. Note that this trick clutters /srv fast, but if you only need to
> apply it once...
factotum is started by the boot process before
cpurc.
- erik
prev parent reply other threads:[~2010-12-14 18:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 13:00 Steve Simon
2010-12-14 13:22 ` erik quanstrom
2010-12-14 13:53 ` Steve Simon
2010-12-14 18:05 ` Nathaniel W Filardo
2010-12-14 18:19 ` erik quanstrom [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=8f2874e1e9314a2a2af78a99b287b018@coraid.com \
--to=quanstro@labs.coraid.com \
--cc=9fans@9fans.net \
/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).