From: "ron minnich" <rminnich@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] I'm puzzled
Date: Tue, 29 May 2007 08:51:11 -0700 [thread overview]
Message-ID: <13426df10705290851s6d2714fbk7bdb3de1a925b119@mail.gmail.com> (raw)
In-Reply-To: <20070529105804.C68B41E8C1C@holo.morphisms.net>
On 5/29/07, Russ Cox <rsc@swtch.com> wrote:
>at least you didn't get EACCES
> or something like that.
yep, you're right.
Anyways, I'm closer, I found that once I had a working factotum on the
node -- i.e. I got the rsa key into the factotum so that tls would
work -- (this is in essence a combined auth/fs/cpu node) then mail
passwords stopped working.
Closer. Will update wiki when I figure this all out.
thanks
ron
prev parent reply other threads:[~2007-05-29 15:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 4:13 ron minnich
2007-05-29 5:48 ` geoff
2007-05-29 5:51 ` andrey mirtchovski
2007-05-29 6:21 ` ron minnich
2007-05-29 11:00 ` Russ Cox
2007-05-29 15:51 ` ron minnich [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=13426df10705290851s6d2714fbk7bdb3de1a925b119@mail.gmail.com \
--to=rminnich@gmail.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).