From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] p9p factotum available for plan 9
Date: Tue, 9 Nov 2010 09:41:26 -0800 [thread overview]
Message-ID: <AANLkTik0LMeWaT5wo2RRWcrzqRz+RX2a_o45UjcFSMgs@mail.gmail.com> (raw)
In-Reply-To: <75ea74312ad96f76de8cd4b3291ffb1d@brasstown.quanstro.net>
[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]
On Mon, Nov 8, 2010 at 7:37 PM, erik quanstrom <quanstro@quanstro.net>wrote:
> On Wed Nov 3 17:15:36 EDT 2010, quanstro@quanstro.net wrote:
> > contrib/install quanstro/nfactotum
> >
> > imap/smtpd passwd and cram and are untested.
>
> imap4d with a password (which uses cram) now works.
> imap4d with a cram challenge does not.
>
> > telnet (server) is known broken. i don't think it's a hard fix.
>
> telnet now works.
>
> - erik
>
>
This is tangential to the topic, but has anyone written up a "how I use p9p"
configuration style document? I've not really tried to use factotum from
p9p, because I was not even sure if it worked.
Also the one time I tried to set up venti from p9p I basically failed
horribly, and wasn't really sure what I did wrong. (I should read the
installation scripts for Plan 9 and the man pages but haven't had time to
get back to it).
I'm wondering things like "can I use p9p venti as a snapshot back end to a
VMWare Plan 9 Fossil?
I'd also like to host the blocks for my guruplug on my Mac OS X system
directly with p9p venti if I could.
I feel I'm missing out on a few really great opportunities to use this
stuff, and I doubt I'm the only one :-).
That said, I use p9p Acme all the time, and it's wonderful!
[-- Attachment #2: Type: text/html, Size: 1813 bytes --]
next prev parent reply other threads:[~2010-11-09 17:41 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 21:13 erik quanstrom
2010-11-09 3:37 ` erik quanstrom
2010-11-09 17:41 ` David Leimbach [this message]
2010-11-09 17:51 ` erik quanstrom
2010-11-10 0:37 ` erik quanstrom
2010-11-10 1:49 ` Russ Cox
2010-11-10 6:46 ` erik quanstrom
2010-11-10 14:31 ` Russ Cox
2010-11-12 3:35 ` Noah Evans
2010-11-12 5:34 ` erik quanstrom
2010-11-12 5:46 ` Noah Evans
2010-11-12 6:03 ` Noah Evans
2010-11-12 6:19 ` Russ Cox
2010-11-12 6:25 ` Noah Evans
2010-11-12 9:07 ` EBo
2010-11-12 15:12 ` David Leimbach
2010-11-12 15:19 ` Eric Van Hensbergen
2010-11-12 15:35 ` erik quanstrom
2010-11-12 15:55 ` Russ Cox
2010-11-12 16:22 ` Eric Van Hensbergen
2010-11-12 19:55 ` ron minnich
2010-11-12 20:23 ` erik quanstrom
2010-11-12 20:31 ` Eric Van Hensbergen
2010-11-12 20:37 ` ron minnich
2010-11-12 20:30 ` Eric Van Hensbergen
2010-11-12 20:41 ` ron minnich
2010-11-12 22:15 ` Eric Van Hensbergen
2010-11-12 22:20 ` ron minnich
2010-11-12 22:36 ` Russ Cox
2010-11-13 8:31 ` tlaronde
2010-11-13 23:42 ` Dave Eckhardt
2010-11-14 22:49 ` Nathaniel W Filardo
2010-11-15 16:22 ` erik quanstrom
2010-11-15 17:40 ` Nathaniel W Filardo
2010-11-15 17:50 ` John Floren
2010-11-12 21:12 ` Russ Cox
2010-11-09 18:08 ` yy
2010-11-09 19:17 ` Bakul Shah
2010-11-09 19:27 ` Russ Cox
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=AANLkTik0LMeWaT5wo2RRWcrzqRz+RX2a_o45UjcFSMgs@mail.gmail.com \
--to=leimy2k@gmail.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).