From: Robert Raschke <rrplan9@tombob.com>
To: 9fans@cse.psu.edu
Subject: [9fans] cpu from Inferno to Plan 9
Date: Wed, 7 Mar 2007 12:40:46 +0000 [thread overview]
Message-ID: <f1cc2393f5f85a3dc1383a67b6906c0d@tombob.com> (raw)
Hi,
I have been using the most fabulous Acme "stand-alone" under Windows
(http://caerwyn.com/acme/) and am now getting into maybe using it to
connect to my home P9 machine. So, for starters I was going try and
cpu from my Inferno Acme into my home Plan 9.
My auth knowledge on all of this is very limited. As far as I
understand, I will need to create myself a key for my Inferno keyring,
for example by using getauthinfo(8). But I also need to have
something listening on my Plan 9 machine on the inflogin port (6673).
What is it I have to configure in my /rc/bin/services?
Can anyone point me in the right direction for setting up both ends to
talk to each other?
Thanks ever so much,
Robby
--
r dot raschke at tombob dot com
next reply other threads:[~2007-03-07 12:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 12:40 Robert Raschke [this message]
2007-03-07 13:05 ` Kris Maglione
2007-03-09 18:18 ` rog
2007-03-09 18:31 ` Charles Forsyth
2007-03-09 18:47 ` David Leimbach
2007-03-09 19:35 ` C H Forsyth
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=f1cc2393f5f85a3dc1383a67b6906c0d@tombob.com \
--to=rrplan9@tombob.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).