Yep, when the "lazy approach" didn't yield an immediate answer, I went
through the commit messages and figured it out a bit ago, and things are
now building.

Just another example of how all this crypto export crap makes life
inconvenient :-( (but on the other hand, perhaps allowing itojun access to
the crypto-us tree to commit that two-character change really *would* have
brought on Armageddon, as the NSA and State Dept. would like us to believe
:-P )

At 10:16 PM 12/21/99 +0100, Assar Westerlund wrote:
>>us/libexec/telnetd/telnetd.c:623: structure has no member named
`__ss_family'
>> *** Error code 1
>
>This is probably due to (us) telnetd not being updated to the this change:
>
>    Module Name:	syssrc
>    Committed By:	itojun
>    Date:		Mon Dec 20 06:18:47 UTC 1999
>
>    Modified Files:
>            syssrc/sys/sys: socket.h
>
>    Log Message:
>    based on recent discussion on ipngwg, use XNET definition for
>    sockaddr_storage.  next revision of RFC2553 will be using this.
>
>    ss_len and ss_family are now available for userland programmers.
>
>So just changing `__ss_family' to `ss_family' should make everything
>work.
>
>/assar
>