From: Jim Choate <ravage@einstein.ssz.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] ssh server?
Date: Sat, 7 Feb 2004 10:12:42 -0600 [thread overview]
Message-ID: <Pine.LNX.4.33.0402071006070.20463-100000@einstein.ssz.com> (raw)
In-Reply-To: <32890.67.85.61.176.1076177966.squirrel@www.infernopark.com>
On Sat, 7 Feb 2004 vdharani@infernopark.com wrote:
> another quick question.
>
> did u say i could ssh to plan 9 box? i tried it but i dont think it works
> for me. do i have to set up ssh server manually? what are the steps i
> should take?
Crank up a auth server and follow the instructions on config'ing ssh for
each user you wish to provide with that server.
I don't remember if this got left in the SysAdmin article but the process
is detailed in the Hangar 18 How To,
http://open-forge.com/hangar18/Plan9Intro.txt
This document explains how to do a single I/O,cpu,auth server using kfs.
This is the first thing you really need to build to create a working P9
cloud. My personal view is that it should be at minimal a three machine
cloud. Two cpu servers, one running I/O and another running auth. The third
will be a fileserver.
Also, if you want to go -from- a P9 box to a non-P9 box you should look
into 'vt'. It will make your life much easier than trying to do it from a
standard rc prompt. This will save you some considerable agravation ;)
-- --
Open Forge, LLC 24/365 Onsite Support for PCs, Networks, & Game Consoles
512-695-4126 (Austin, Tx.) help@open-forge.com irc.open-forge.com
Hangar 18 Open Source Distributed Computing Using Plan 9 & Linux
512-451-7087 http://open-forge.org/hangar18 irc.open-forge.org
James Choate 512-451-7087 ravage@ssz.com jchoate@open-forge.com
next prev parent reply other threads:[~2004-02-07 16:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-07 18:19 vdharani
2004-02-07 16:12 ` Jim Choate [this message]
2004-02-07 21:09 ` Micah Stetson
2004-02-08 1:21 ` Jim Choate
2004-02-08 18:59 ` Jack Johnson
2004-02-09 17:08 ` Micah Stetson
2004-02-09 17:46 ` a
2004-02-08 4:56 ` boyd, rounin
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=Pine.LNX.4.33.0402071006070.20463-100000@einstein.ssz.com \
--to=ravage@einstein.ssz.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).