9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Stephen Wynne <stevemw@place.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: [9fans] cpuserver: dhcp for authsrv, rio, users, ssh, factotum, pull
Date: Sat,  3 Jul 2004 00:17:01 -0700	[thread overview]
Message-ID: <40E65D6D.4050101@place.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0406251129360.22766-100000@maxroach.lanl.gov>

I'm attempting to setup both a cpuserver and an authserver on
one system. I'd like it to be a terminal, too.

First, I more or less followed the advice on it at
http://www.cs.bell-labs.com/wiki/plan9/Configuring_a_Standalone_CPU_Server
while also looking at
http://pages.cpsc.ucalgary.ca/~mirtchov/lanlp9/4e/cpuauth.html

This may sound funny, but can I setup a CPU server, auth server,
and terminal all on the same system and have it all configure
itself dynamically based on a DHCP IP address?

Although my system worked just fine from the gnot install defaults,
after converting to a cpuserver,  I got this:

    RIO says: aux/vga: mga2164w: can't set mga type
    rio: can't open display: initdisplpay: /dev/draw/new: no framebuffer
    init: rc exit status: rc 12: rio 13: display open

Adding lines of display setup logic from from termrc didn't help.

I am unclear what passwords to assign to secstore and
bootes as I'm setting up the authserver for the first time.
I'm also unclear what the difference is between bootes
and other users I might create after this.

Also, SSH fails to connect now that I've rebooted and
setup bootes as the terminal "owner" (if that's the right term,
pardon my pun). I figure something must be haywire
in my authentication (Factotum?). Following instructions at
http://pages.cpsc.ucalgary.ca/~mirtchov/lanlp9/tips.html
I figured I should combine both authserver and terminal
instructions. I get:

    cpu% auth/secstore -p /tmp/factotum
    can't dial tcp!$auth!5356
    secstore authentication failed

Out of curiosity, I tried to do a pull to update my system.
That didn't work, either. I was running as bootes connected
through drawterm:

cpu% /usr/glenda/bin/rc/pull
post...
srv tcp!sources.cs.bell-labs.com!9fs: mount failed: authentication failed
bind: /n/sources/plan9: '/n/sources/plan9' does not exist
servermount: bind 363: bind
cpu% 9fs sources
srv tcp!sources.cs.bell-labs.com: mount failed: authentication failed

I apologize for asking so many questions at once, but there
doesn't seem to be a true cookbook recipe posted on just
how to do this with all the obvious steps included for mortals
like me.

One problem I hit was trying to setup fossil by default on this
system. There were exceptions to the flow of the normal KFS
setup that threw me off and I was in a hurry.

I have something else I want to do that I was almost able to do
with a plain KFS gnot install, so I'm tempted to just do it
over again and get back to that...

By the way, can I reboot a system from drawterm and how would I
do that?

My cpurc is at http://www.place.org/~stevemw/junk/cpurc
The ftpfs command is really handy!


  parent reply	other threads:[~2004-07-03  7:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-25 17:30 [9fans] which register is used as FP on the x86 ron minnich
2004-06-25 17:53 ` rog
2004-06-26 11:56   ` Andrew Lynch
2004-06-26 12:35     ` Latchesar Ionkov
2004-06-26 12:35     ` Charles Forsyth
2004-06-26 14:27   ` Latchesar Ionkov
2004-06-26 17:31     ` Charles Forsyth
2004-07-03  7:17 ` Stephen Wynne [this message]
2004-07-03 16:37   ` [9fans] andrey mirtchovski
2004-07-05  4:06     ` [9fans] Stephen Wynne
2004-07-05 17:23       ` [9fans] andrey mirtchovski
2004-07-05 20:33       ` [9fans] Eric Grosse

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=40E65D6D.4050101@place.org \
    --to=stevemw@place.org \
    --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).