9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Gregory Pavelcak <pavelcak@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] CPU Server Wiki, auth/keyfs, and password for the machine.
Date: Sun, 27 Jul 2008 09:33:05 -0400	[thread overview]
Message-ID: <3E858CEB-88B4-40CD-A81A-8B993FBA869E@gmail.com> (raw)
In-Reply-To: <20080726190827.1EA211E8C1C@holo.morphisms.net>


On Jul 26, 2008, at 3:10 PM, Russ Cox wrote:
>>
>
> You can test connectivity using aux/9pcon:
>
> 	cpu% aux/9pcon -n tcp!web.mit.edu!9fs
> 	aux/9pcon: dial: connection refused
> 	cpu%
>
> If it does connect (which I doubt)

Correct.

brain# aux/9pcon -n il!192.168.0.108!9fs
aux/9pcon: dial: connection rejected

Interesting thing here. I'm working on a standalone CPU/Auth server
so that I can mount my file server and populate it. (I had a recent
question about recovering from an old pseudo worm, but after trying
for a while, I became convinced that I had used those disks when I
messed around with DragonFlyBSD, and I re-reamed). So, the kernel I'm
trying is based on pccpuf. In anticipation of taking /root from the
file server, I also made a kernel based on pccpu. I did the same
thing to both: added "il" under "ip" and under "boot" (of course
that's just uncommenting in pccpu), put il.c in /sys/src/9/ip/, and
added Logil and Logilmsg to ip.h. Build went fine. Copy to 9fat.
Menuitems in plan9.ini, and I'm good to go.

The reason I'm boring you with that information, and the part I found
interesting, is this. Just for the heck of it I selected my "CPU,
File Server Root" option, i.e. I booted from 9pccpu instead of
9pccpuf. Of course, the CPU server reboots because there are no files
on the file server yet, but I do seem to get past the il connection
in this case. The file server says:

	il: allocating il!192.168.0.109!43095
	authentication failed: NeedTicket: unknown user
	hangup connection timed out-3 43095/192.168.0.109.17008

Gee. Nice to have some indication that I will have authentication
issues too, once I get il to connect.

Any thoughts (other than "man you really botched this
installation!") :-)

Greg



  reply	other threads:[~2008-07-27 13:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-26 13:40 g.pavelcak
2008-07-26 16:15 ` Russ Cox
2008-07-26 18:28   ` Gregory Pavelcak
2008-07-26 18:50     ` [9fans] CPU Server Wiki, auth/keyfs, erik quanstrom
2008-07-26 19:10     ` [9fans] CPU Server Wiki, auth/keyfs, and password for the machine Russ Cox
2008-07-27 13:33       ` Gregory Pavelcak [this message]
2008-07-27 14:42         ` [9fans] CPU Server Wiki, auth/keyfs, erik quanstrom
2008-07-27 14:55         ` Skip Tavakkolian
2008-07-27 15:40           ` Gregory Pavelcak
2008-07-27 16:48             ` erik quanstrom
2008-07-28 10:17               ` Gregory Pavelcak
2008-07-28 10:49                 ` erik quanstrom

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=3E858CEB-88B4-40CD-A81A-8B993FBA869E@gmail.com \
    --to=pavelcak@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).