From mboxrd@z Thu Jan 1 00:00:00 1970 From: presotto@plan9.bell-labs.com Message-Id: <200006131422.KAA07293@cse.psu.edu> Date: Tue, 13 Jun 2000 10:22:27 -0400 To: alteridentity@yahoo.com, 9fans@cse.psu.edu Subject: Re: [9fans] Experiences Installing Version 3: Another Take MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-zsqhhknyoawpriwjdbkpwuhswy" Topicbox-Message-UUID: b957c4b8-eac8-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-zsqhhknyoawpriwjdbkpwuhswy Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit ipnet=amigo-net ip=192.168.1.0 dns=151.164.1.7 dns=151.164.1.8 ipgw=192.168.1.254 ip=192.168.1.4 sys=tor ip=192.168.1.2 sys=plastique ip=192.168.1.3 sys=dock ip=192.168.1.7 sys=plan9 proto=il This should be enough to make you a happy camper. If you have a list of domain names you'ld like to search through when resolving names ammend the first entry to: ipnet=amigo-net ip=192.168.1.0 dns=151.164.1.7 dns=151.164.1.8 ipgw=192.168.1.254 dnsdomain=x.y.z dnsdomain=a.b.c where x.y.z and a.b.c are domain suffixes. If you have domain names that these systems are reachable by add a dom=my.domain.name atribute value pair to the system entries where my.domain.name is the full domain name of the system. If you have a DHCP server on your net, you'ld get most of the entry for your system by cating /net/ndb which is a turd our ipconfig leaves around for other programs to use. --upas-zsqhhknyoawpriwjdbkpwuhswy Content-Type: message/rfc822 Content-Disposition: inline Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Tue Jun 13 05:52:36 EDT 2000 Received: from cse.psu.edu ([130.203.3.50]) by plan9; Tue Jun 13 05:52:35 EDT 2000 Received: from localhost (majordom@localhost) by cse.psu.edu (8.8.8/8.8.8) with SMTP id FAA00008; Tue, 13 Jun 2000 05:33:33 -0400 (EDT) Received: by claven.cse.psu.edu (bulk_mailer v1.5); Tue, 13 Jun 2000 05:32:39 -0400 Received: (from majordom@localhost) by cse.psu.edu (8.8.8/8.8.8) id FAA29774 for 9fans-outgoing; Tue, 13 Jun 2000 05:32:00 -0400 (EDT) X-Authentication-Warning: claven.cse.psu.edu: majordom set sender to owner-9fans using -f Received: from mercury.bath.ac.uk (mercury.bath.ac.uk [138.38.32.81]) by cse.psu.edu (8.8.8/8.8.8) with ESMTP id FAA29725 for <9fans@cse.psu.edu>; Tue, 13 Jun 2000 05:31:36 -0400 (EDT) Received: from news by mercury.bath.ac.uk with local (Exim 3.12 #1) id 131msw-0003AW-00 for 9fans@cse.psu.edu; Tue, 13 Jun 2000 10:21:26 +0100 Received: from GATEWAY by bath.ac.uk with netnews for 9fans@cse.psu.edu (9fans@cse.psu.edu) To: 9fans@cse.psu.edu Date: Tue, 13 Jun 2000 09:10:09 GMT From: "James G. Stallings II" Message-ID: <39454B37.4ECB8A63@yahoo.com> Organization: SBC Internet Services Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [9fans] Experiences Installing Version 3: Another Take Sender: owner-9fans@cse.psu.edu Reply-To: 9fans@cse.psu.edu Precedence: bulk Greetings, fellow users of the oracle that is USEnet! This post chronicles my adventures installing and (mis)configuring the latest release of plan9 (R3). I will summarize it as follows: as usual, getting the hardware to work is 98% of success. Of course, you have to be able to tell it (plan9) what and where the hardware is, but that's the other two percent, huh :) Once I'd cobbled together the parts for a suitably old machine to set it up on, I got the baseline hardware working and was able to boot to the graphic install. The old dog is built up as follows: 486DX2 66 from Cyrix on an unknown MB w 32M ram 512M Conner HD (IDE) 36x CDROM LinkSys Ether16CT 10BT ethernet std 1.4M floppy SB16 audio std kb 2 button ser mouse Speedstar64 VGA with about 511K of memory on it (some of the pixels drop out ;^) Initial installs were done via locally-burned CD. The fifth and final install was performed over the ether and is installed on a native plan9 fat on the disk (it's the only partition). As I summarized, getting the hardware right has been most of the battle so far. This would have been no different for any other O/S. Getting the right VGA settings was nontrivial enough to educate me concerning getting the ethernet right. Jim (jmk@plan9.bell-labs.com) was an especially valuable resource here as well - Thanks Amigo! Now I have it pretty well going, except for a few issues involving networking. Can someone tell a bonehead how to configure the /lib/nbd/ for a small lan? The net is like this: 1 win95 box named tor at 192.168.1.4 1 dual boot win95/redhat box named nitro at 192.168.1.1 1 debian server named plastique at 192.168.1.2 1 winnt portable named dock at 192.168.1.3 1 standalone plan9 box named plan9 at 192.168.1.7 gateway is 192.168.1.254 dns is 151.164.1.7 and 151.164.1.8 the plan9 box (for now) needs to be everything plan9 on the lan (cpu server, file server and terminal) I'd be happy to share my current /lib/ndb/local* and /lib/ndb/common with you except that in my feeble attempts to configure it I've blown the box off the 'net. I know it's not a device problem cause it werked just fine when I downloaded the distribution archive. Plus it was pingable until I munged with /lib/nbd/* Thanks in advance for any assists! Cheers! James --upas-zsqhhknyoawpriwjdbkpwuhswy--