From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <09B9A3AC-3D0C-4562-92C0-1B373B31DADA@xmission.com> References: <475051C5-92F9-42B8-AC80-3EAA7E08EBE0@xmission.com> <09B9A3AC-3D0C-4562-92C0-1B373B31DADA@xmission.com> Date: Thu, 9 Dec 2010 19:54:17 -0500 Message-ID: From: John Floren To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] have installed plan 9 on many hosts, can't get any of them to "share". Topicbox-Message-UUID: 8a9893f6-ead6-11e9-9d60-3106f5b1d025 On Thu, Dec 9, 2010 at 7:39 PM, Lloyd Caldwell wrote: > > John, thanks, > >> >> If you follow the standalone CPU installation instructions on the wiki >> to the letter, you will have a cpu/auth/file server. It's then easy to >> export fossil to clients, just set up the configuration to listen on >> the appropriate port (the document you want is linked from the >> standalone instructions). > > I followed it to the letter. It has mistakes or inconsistencies (i think?= ). > for example it says: > =C2=A0 =C2=A0 =C2=A0 =C2=A0proto=3Dil - recommended (isn't this obsolete?= ) > =C2=A0 =C2=A0 =C2=A0 =C2=A0bootf=3D/386/9pc (It should be bootf=3D/386/9p= xeload) il is obsoleted, although a few people do still use it. I have never used the proto=3D attribute, don't think you need it. You want to set bootf=3D/386/9pxeload for the systems that you want to netboot, for the others you don't have to set the attribute. > the bind loop doesn't work with 9pccpuf kernel from install cdrom (circa = dec > 2009): > =C2=A0 =C2=A0 =C2=A0 =C2=A0for (i in m i S t) > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0bind -a '#'^$i /de= v >/dev/null >[2=3D1] > fails, complains of no frame buffer (this is from the installation kernel > /386/9pccpuf). =C2=A0This means no rio on server console so fixing things > requires rebooting into a terminal kernel (I actually know sed quite well > but one gets tired of sed 's/foo/bar/' =C2=A0filename >j ; mv j filename = :-). > I put this in the wiki a bit ago: "In this case we have m (mouse), i (draw), S (sd - disk), and t (uart - serial); if you get errors about /dev/realmode, include P in this list". If you're not getting /dev/realmode complaints, I guess it must be something else. > there is no file /rc/bin/service/tcp567 (install image from dec 2009) If it's not there, don't worry about it! I think this might be a double-check thing, or it might just be an old instruction. > The example of a combined cpu/auth server, is not consistent, it actually= is > not combined, unless I'm reading it wrong auth is different then cpu. An > excerpt from the 'Configuring a standalone CPU server' wiki page (cut and > pasted at 5:17pm mst today): > > A simple example for a combined cpu/auth server, the 192.168.1.100 machin= e, > could be: > > ipnet=3Dmynet ip=3D192.168.1.0 ipmask=3D255.255.255.0 > =C2=A0 =C2=A0 =C2=A0 =C2=A0auth=3Dbouncer > =C2=A0 =C2=A0 =C2=A0 =C2=A0cpu=3Dcycles > =C2=A0 =C2=A0 =C2=A0 =C2=A0dns=3Dlookup > =C2=A0 =C2=A0 =C2=A0 =C2=A0dnsdom=3D9fans.net > > authdom=3D9fans.net auth=3Dbouncer > > ip=3D192.168.1.100 sys=3Dbouncer dom=3Dbouncer.9fans.net > ip=3D192.168.1.101 sys=3Dcycles dom=3Dcycles.9fans.net > ip=3D192.168.1.102 sys=3Dlookup dom=3Dlookup.9fans.net > What that configuration says is that the *default* cpu server is cycles. That doesn't necessarily mean bouncer isn't a cpu server too. > >> >> Then, once you've got that set up, you install a terminal on another >> machine. When it asks for a root, say "tcp" then give it the IP for >> your standalone server when it asks. Boom, your terminal now has >> remote root. You'll probably want to configure /lib/ndb/local to keep >> track of all your systems... >> >> Configuring PXE isn't that tricky but I don't want to run through the >> setup process right now, let me know if you need a rundown. > > > If I boot this box from install cdrom and it can obtain ip address from > dhcpd server running on cpu/auth/fs box and see that fs and auth are setu= p > correctly. =C2=A0If I attempt to use cpu command from cdrom booted termin= al I get > the following error when attempting to connect to 10.0.1.6 (my combined > cpu/auth/fs server). > > term% cpu -h 10.0.1.6 -u lmc > cpu: can't authenticate: 10.0.1.6: auth_proxy rpc write: p9sk1@p9-net: > auth_getkey: no /factotum or /boot/factotum: didn't get key !password? > dom=3Dp9-net proto=3Dp9s > > the cpu/auth/fs server /lib/ndb/local file is: > > #--- start of /lib/ndb/local > ip=3D127.0.0.1 sys=3Dlocalhost dom=3Dlocalhost > > ipnet=3Dp9-net ip=3D10.0.1.0 ipmask=3D255.255.255.0 > =C2=A0 =C2=A0 =C2=A0 =C2=A0auth=3Dxeon0.p9.net > =C2=A0 =C2=A0 =C2=A0 =C2=A0cpu=3Dxeon0.p9.net > =C2=A0 =C2=A0 =C2=A0 =C2=A0fs=3Dxeon0.p9.net > > authdom=3Dp9-net auth=3Dxeon0.p9.net > > ip=3D10.0.1.6 sys=3Dxeon0 dom=3Dxeon0.p9.net ether=3D0007e933c735 > > ip=3D10.0.1.7 sys=3Dxeon1 dom=3Dxeon1.p9.net ether=3D0007e933ca35 > =C2=A0 =C2=A0 =C2=A0 =C2=A0bootf=3D/386/9pxeload > > #--- end of /lib/ndb/local > > the plan9.ini file for xeon1 is in /cfg/pxe/0007e933ca35 and contains: > > #--- start of xeon1 plan9.ini diskless boot config > > nobootprompt=3Dether0!/386/9pc > mouseport=3Dps2intellimouse > monitor=3Dxga > vgasize=3D1024x768x16 > > #-- end of /cfg/pxe/0007e933ca35 I'm not sure if this is going to work with the cdrom-booted machine. It isn't going to have the /lib/ndb/local file, right? So it doesn't know what the auth server is... I might be mis-reading the situation. > >> >> Basically, "> Where might I go for a walk thru in setting up a simple >> plan9 installation one cpu/auth/fs and one terminal?" is answered by >> "Use the standalone install instructions... and that's basically it." >> >> If you'd give us the errors you're seeing from cpu, we might be able >> to help. "Weird errors" isn't very informative! >> > --> Error message from net booting. > > Intel(R) Boot Agent FE v4.1.16 > Copyright (C) 1997-2004, Intel Corporation > > CLIENT MAC ADDR: 00 07 E9 33 CA 35 GUID: 18B58355 0CDA DA11 0080 > 35CA33E90700 > CLIENT IP: 10.0.1.7 =C2=A0MASK: 255.255.255.0 =C2=A0DHCP IP: 10.0.1.6 > > Plan 9 from Bell Labs by PXE > ELCR: 0E20 > pcirouting: 8086/2483 at pin 2 irq 9 > FLAGS=3D10292 TRAP=3De ECODE=3D0 PC=3D8000a9b3 > =C2=A0AX f000eef3 =C2=A0 BX 00000200 =C2=A0CX 00000000 =C2=A0 =C2=A0DX 80= 802798 > =C2=A0SI 80057e3c =C2=A0DI 00000000 =C2=A0 BP 00000000 > =C2=A0CS 0010 DS 0008 =C2=A0 ES 0008 =C2=A0 FS 0008 =C2=A0GS 0008 > =C2=A0CR0 80000011 CR2 f000eefb CR3 00094000 > panic: exception/interrupt 14 > > Press almost any key to reset.._ > > <-- End error message from net booting. > I can successfully net boot, linux, freebsd and msdos on this box. =C2=A0= I get > roughly the same errors (different register values) on other boxes. =C2= =A0I have > via epia-m boxes, intel dual xeon boxes, amd64 dual processor boxes and > older pentium 4 boxes. 9pxeload fails similarly on all of them. =C2=A0I s= wapped > out the network switch and also tried a "dumb" hub. > > I tried net loading 9pxeloaddebug but the box hangs after getting it's ip > address, i.e. no 'Plan 9 from Bell Labs by PXE' banner. > >> If it comes down to it, I can exchange some of my config files with >> you. I have a standalone cpu server running, with PXE boot working > > Maybe instead of focusing on net booting. =C2=A0Are there instructions on= how to > connect from one standalone system to another? =C2=A0cpu doesn't seem to = work. > =C2=A0If I knew I could actually login to a remote box that would probabl= y help? > =C2=A0Maybe not? =C2=A0I'm probably thinking about plan 9 all wrong. > > anyway thanks. > Regards > Lloyd > >> >> John >> I'm not exactly sure what's going on with the netbooting problem. The other best solution is this: * Install Plan 9 on your terminal machine (to the hard drive) * When you boot, tell it to get root from TCP and give it the appropriate IPs (10.0.1.6 in your case) * Now you have a terminal sharing the root of the server. You can also cpu if you need, but it's not as big of a deal when you share a root. John