From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: Re: [9fans] interaction of net.alt and factotum
Date: Tue, 14 Dec 2010 13:53:51 +0000 [thread overview]
Message-ID: <2a173e99984fb766349cefccf5a65362@quintile.net> (raw)
In-Reply-To: <b5ffe9f719b5fb2d001be04825bf7428@brasstown.quanstro.net>
[60 files]
> what about building /net.alt in /lib/namespace or /lib/namespace.$machine?
I think there is another wrinkle I forgot to mention, when I import my /net.alt I
do this over an authenticated connection to another plan9 machine. This needs
my key which is held in factotum, so factotum must be already running.
Factotum doesn't get its keys until I manualy extract them from secstore
and write them to /mnt/factotum/ctl, it would be at this point I would
have to inject a namespace change to factotum.
I suspose I could add /mnt/factotum/ns file which I could write to after loading the keys.
All feels a bit clunky.
-Steve
next prev parent reply other threads:[~2010-12-14 13:53 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 [this message]
2010-12-14 18:05 ` Nathaniel W Filardo
2010-12-14 18:19 ` erik quanstrom
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=2a173e99984fb766349cefccf5a65362@quintile.net \
--to=steve@quintile.net \
--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).