Re: sa_len and sin_len

• Next message: Alan Cox: "Re: source of shapecfg.c"
• Previous message: Andrei V.Loukinykh: "aliases & uucp-dom"
• In reply to: Du Jinsong: "sa_len and sin_len"
• Next in thread: Matti Aarnio: "Re: sa_len and sin_len"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> But when porting applications from BSD to Linux, how to circumvent this
> problem?
> In linux: /usr/include/bits/sockaddr.h:
> #define SA_LEN(_x)
>
> But it seems that this is not usable when trying to convert something
> like ifrp->ifr_addr.sa_len , and how about sin_len?

We have no notion of sa_len. Linux is compatible with the traditional socket interface
not with the 4.4BSD extensions. POSIX 1003.1g draft 6.5 says sa_len is optional. We
opt not to have it

-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.rutgers.edu

• Next message: Alan Cox: "Re: source of shapecfg.c"
• Previous message: Andrei V.Loukinykh: "aliases & uucp-dom"
• In reply to: Du Jinsong: "sa_len and sin_len"
• Next in thread: Matti Aarnio: "Re: sa_len and sin_len"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Fri Jan 07 2000 - 21:00:13 EST