To: Colin Wood <ender@is.rice.edu>
From: Stewart King <slking@hcs.harvard.edu>
List: port-mac68k
Date: 01/20/1997 19:05:15
> first. Here's more or less what I have in /etc/hosts:
> 127.0.0.1 localhost loopback
> 128.42.154.39 mycroft-holmes.brown.rice.edu mycroft-holmes mh
> And so, my /etc/hostname.ae0 has:
> inet mycroft-holmes 255.255.255.0 128.42.154.255 up
> Where the 255's are my netmask and the other is my gateway address.
This did, in fact, make those errors go away. Unsurprisingly, I now have
an exciting, new batch of errors to report.
starting network
add host host12: gateway localhost
writing to routing socket: Invalid argument
add net : Invalid argument
And telnet still has no route to remote hosts. I used the same gateway
address from the old MacTCP settings, although it's possible that I
didn't put it everywhere that I should have. Hum.
Isn't there some way to make all of this more obvious to set up? Or would
that be against the spirit of the thing? Am I cheating on some sort of
Unix club initiation rite? "If he can't make telnet work we don't want
the little spiker."
stewart.