The git@xxxxxxxxx address is the one subscribed to this list, to make
it easy for us to filter list messages into shared folders. Because
we manage so many packages, one or other of us will drop in and out of
contact on the relevant lists depending what package we happen to be
working on.
Anyway, you can always put a post directly in my INBOX by Cc:ing
gary@xxxxxxxxxxxxxxxxxx and/or gary@xxxxxxx if you'd like to be sure
that I will read something. :)
On Mon, Mar 15, 2010 at 04:42:57PM -0500, Brandon Casey wrote:
> I expect that the layout of the sockaddr_* family of structures will
> follow the layout of struct sockaddr, otherwise they wouldn't be
> compatible.
>
> In other words, I think that if struct sockaddr looks like this:
>
> struct sockaddr {
> uchar_t sa_len; /* total length */
> sa_family_t sa_family; /* address family */
> char sa_data[14]; /* actually longer; address value */
> };
>
> then somewhere else, struct sockaddr_in looks like this:
>
> struct sockaddr_in {
> uchar_t sin_len;
> sin_family_t sin_family;
> sin_port;
> sin_addr;
> ...
> };
> On 03/15/2010 04:29 PM, Jeff King wrote:
> > Or am I wrong in assuming that, and on AIX sockaddr_in actually has
> > sa_len at the front, so casting to sockaddr does the right thing (and my
> > recommendation above would actually be broken)? The AIX boxen I have
> > access to are all down at the moment.
>
> Maybe Gary can check for us... Gary, what does the declaration for
> struct sockaddr_in look like in your AIX header file?
/usr/include/netinet/in.h excerpt:
/*
* Socket address, internet style.
*/
struct sockaddr_in {
uchar_t sin_len;
sa_family_t sin_family;
in_port_t sin_port;
struct in_addr sin_addr;
uchar_t sin_zero[8];
};
Cheers,
--
Gary V. Vaughan (gary@xxxxxxxxxxxxxxxxxx)
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html