Re: [9fans] Experiences Installing Version 3: Another Take

Re: [9fans] Experiences Installing Version 3: Another Take

[presotto]

	netstat -in
or
	cat /net/ipifc/*/status

will show you what your address
really is, what it thinks the network mask is, etc.

Someone may indeed be answering your dhcp requests.  If you
want to see what dhcp is learning, you can run by hand

	ip/ipconfig -dDn

It'll print out the results of the dhcp steps.  you'll see the
server giving you info.  You cat see the final results of
the dhcp with

	cat /net/ndb

Finally, to override dhcp completely, change the ipconfig entry
in your /rc/bin/termrc with:

	ip/ipconfig -g xxx 192.168.1.7 255.255.255.0

here xxx is the ip address of your gateway.  I forgot was it was
in your previous message

Re: [9fans] Experiences Installing Version 3: Another Take

[James G. Stallings II]

Dude that's pure beauty.

Muchas Gracias Amigo!
-James


presotto@plan9.bell-labs.com wrote:

>         netstat -in
> or
>         cat /net/ipifc/*/status
>
> will show you what your address
> really is, what it thinks the network mask is, etc.
>
> Someone may indeed be answering your dhcp requests.  If you
> want to see what dhcp is learning, you can run by hand
>
>         ip/ipconfig -dDn
>
> It'll print out the results of the dhcp steps.  you'll see the
> server giving you info.  You cat see the final results of
> the dhcp with
>
>         cat /net/ndb
>
> Finally, to override dhcp completely, change the ipconfig entry
> in your /rc/bin/termrc with:
>
>         ip/ipconfig -g xxx 192.168.1.7 255.255.255.0
>
> here xxx is the ip address of your gateway.  I forgot was it was
> in your previous message


__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

Re: [9fans] Experiences Installing Version 3: Another Take

[James G. Stallings II]

By any chance could the referenced "turd" =^) be causing my system to use
dhcp in spite of my other configuration efforts? There is dhcp on my network
somewhere...

Even after syncing my /lib/ndb/local with your suggestions, the system comes
up addressed at 192.168.1.5 instead of 192.168.1.7. I determined this by
looking at /net/iptab and /net/iproute and then attempting a ping of both the
.5 and .7 addresses. The machine is on .5

Thanks Man!

James

presotto@plan9.bell-labs.com wrote:

> 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.


__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

Re: [9fans] Experiences Installing Version 3: Another Take

[presotto]

[-- Attachment #1: Type: text/plain, Size: 927 bytes --]

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.

[-- Attachment #2: Type: message/rfc822, Size: 3829 bytes --]

From: "James G. Stallings II" <alteridentity@yahoo.com>
To: 9fans@cse.psu.edu
Subject: [9fans] Experiences Installing Version 3: Another Take
Date: Tue, 13 Jun 2000 09:10:09 GMT
Message-ID: <39454B37.4ECB8A63@yahoo.com>

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

[9fans] Experiences Installing Version 3: Another Take

[James G. Stallings II]

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