> 	The only real difference being the usage of
> 	"sockaddr_in" instead of "osockaddr".

a comments on this:

in my opinion, using sockaddr_in (in my opinion) is Just Plain Wrong.
It should either be using a (new) 'struct sockaddr', or an old 'struct
sockaddr' (i.e. a 'struct osockaddr').

> 	Is this a question of SYSV vs. BSD or would
> 	be sensible to change NetBSD to use sockaddr_in
> 	instead ?

I just spent some time looking around on various machines, and i
couldn't find any that used sockaddr_in.

I looked on:
	SunOS (uses 'struct sockaddr', but that's the old sockaddr)
	ULTRIX (again, uses struct sockaddr, with the old sockaddr)
	DEC OSF/1 (uses 'struct osockaddr')
	Mach 2.6 (uses 'struct sockaddr, with old sockaddr)
	HP/UX (couldn't find any apprently-talk-related files under
		/usr/include 8-)

of course, some of those aren't necessarily 'new' talk...  8-)


i've not yet found a system that used sockaddr_in's in talkd.h, though
i don't have access to any "pure-SysV systems."

Given that, and given the fact that talk apparently _has_
standardized on using the old struct sockaddr, and given my opinion
that using 'sockaddr_in' is incorrect anyway, i don't think it's
reasonable to change, unless somebody can point me at something
(e.g. an RFC) that says that 'sockaddr_in' is appropriate.


chris