From: baruch@nynexst.com (Robert Baruch) Subject: net-2 config solved...sort of Date: Thu, 10 Jun 1993 20:45:24 GMT
OK, I know there has been a lot of asking about how to configure net-2 stuff. I
was in the same boat. But I think I have my stuff configured correctly now --
at least bootup yields no more errors, and I can make a server/client program
which actually connects.
Bear in mind that I have NO network at all. I'm just gonna use the "loopback"
interface. You're on your own w/r to me if you want ether stuff.
Here's what I had to do:
(1) Get 99pl10. Compile it. Reboot. You'll get errors because the new kernel
contains the new network stuff.
(2) Get libc.so.4.4.1 and libm.so.4.4.1 and link them in to the usual place in /lib.
Remember to do it right! i.e., ln -sf libc.so.4.4.1 libc.so.4
(3) Now you're ready to install the net-2 binaries. Go to tsx-11.mit.edu and
go to /pub/linux/packages/net/net-2/binaries and get all three files there.
Also go to packages/net/net-2/? (I forget the exact directory) and get
net-010.tar.z.
(4) mkdir /conf/net. This next step is kind of ad-hoc:
(5) copy everything from /etc/inet to /conf/net. Now tar tvf net-base.tar and
find out all the links it's gonna make. Make sure it can make them by seeing
if there are any files which are already there. If they are, move them to
where the link will point to. Make any directories within /conf/net as
required.
(6) tar xvf net-base.tar
(7) tar xvf net-std.tar
(8) I'm not sure what net-010 will do for you...
(9) mkdir /var/log; touch /var/log/notice (if you don't already have it)
(10) check to see that /etc/services is correct. Mine for some reason had a link
to itself rather than /etc/inet/services.
(11) joe /etc/networks
In this file put:
loopback 127.0.0.0
localnet 192.0.2.0
(12) joe /etc/rc.local
For the hostname line, make sure it reads:
hostname -vS
(13) joe /etc/HOSTNAME
Stick your host's name in here.
(14) joe /etc/rc.net
Get rid of the lines with config in them, and do:
/etc/ifconfig lo 192.0.2.128 netmask 255.0.0.0
/etc/route add localnet
(15) reboot. Hopefully there should be no errors now. I really can't give you
any more help than that. Hopefully this gives you all some kind of jump
point to work from!
Good luck!
--Rob