[comp.unix.aux] Why doesn't talk work???

alexis@panix.uucp (Alexis Rosen) (11/13/90)

Talk must surely have the most infuriating error messages ever devised. Like

You don't exist. Go away.
	or
This host doesn't exist. Boy, am I confused!

Lovely. At least the second one was easy enough to fix. The big question of
the day is, why won't it work now? It's giving me an almost-helpful message,
too. It says:
[Couldn't bind to control socket : Can't assign requested address (69)]

Thanks a lot. _Why_ can't you...

I'd really like to know what's wrong here. The really anoying thing is,
it used to work just fine. Why doesn't it work now?

inetd is running, as is portmap. But I know nothing about this stuff, so I
might be missing something abvious. Help! {insert drowning noises}

Now I've got an even stranger problem. On another Mac, I can't get portmap
or inetd to run. module_dump shows bnet installed, but the various networking
drivers (elap, ddp, llap, and the at* modules) are gone (it's a slip-only
mac). Is this wrong? How can I make things work the way they should???

Thanks,
---
Alexis Rosen
Owner/Sysadmin, PANIX Public Access Unix, NY
{cmcl2,apple}!panix!alexis