From: Luke Evans <luke.evans@gmail.com>
To: 9fans@9fans.net
Subject: [9fans] Canonical way to configure permanent remote cpu access
Date: Mon, 10 Dec 2012 09:37:39 +0000 [thread overview]
Message-ID: <af8207d7-56a5-4cb4-bd11-546ce6c86dd1@googlegroups.com> (raw)
After many years of knowing about Plan 9 but apparently being too lazy to go find out about it, we now have it available on the Raspberry Pi (hurrah!). The ease with which I can now install and learn about Plan 9 is now such that I have no excuse but to dive in :-)
Having got Plan 9 running on the Pi with the networking functioning and having also compiled the version of drawterm for Mac OS X cocoa, I'm now wishing to configure Plan 9 so that it permanently allows access from remote terminals for authenticated users.
I've found a way to achieve this temporarily from the console:
echo 'key proto=p9sk1 dom=plan9 user=glenda !password=MYPASS' >/mnt/factotum/ctl
aux/listen1 -t tcp!*!ncpu /bin/cpu -R &
This works great, but obviously does not survive a reboot of the system. I'd like to know:
- Where's the right place to configure a permanent listener in the config/startup files?
- How should authentication be also permanently configured for any user that should be able to connect with drawterm?
Thanks in advance.
-- Luke
P.S. Apologies if this ends up being the second posting to the group on this subject, I used the Google Groups web front end to post and it announced that it may not have managed to post my original submission after quite a wait. Trying again after several hours and no sign of my post.
next reply other threads:[~2012-12-10 9:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 9:37 Luke Evans [this message]
2012-12-10 10:12 ` lucio
2012-12-10 11:30 ` Richard Miller
2012-12-10 11:38 ` Charles Forsyth
2012-12-10 11:53 ` Richard Miller
2012-12-10 12:02 ` lucio
2012-12-10 15:41 ` Anthony Sorace
2012-12-10 16:47 ` Bakul Shah
2012-12-11 5:43 ` hiro
2012-12-10 11:23 ` Richard Miller
2012-12-11 9:36 ` [9fans] Canonical way to configure permanent remote Luke Evans
2012-12-11 12:21 ` Richard Miller
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=af8207d7-56a5-4cb4-bd11-546ce6c86dd1@googlegroups.com \
--to=luke.evans@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).