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
