Path: utzoo!attcan!uunet!samsung!zaphod.mps.ohio-state.edu!mips!apple!agate!agate.berkeley.edu!rob From: rob@violet.berkeley.edu (Rob Robertson) Newsgroups: comp.unix.wizards Subject: Re: Differences between Berkley 4.2 and 4.3 Message-ID: Date: 17 Dec 89 09:36:24 GMT References: <301@fltk.UUCP> <7422@hubcap.clemson.edu> Sender: usenet@agate.berkeley.edu (USENET Administrator;;;;ZU44) Organization: University of California, Berkeley Lines: 28 In-reply-to: hubcap@hubcap.clemson.edu's message of 14 Dec 89 14:20:39 GMT In article <7422@hubcap.clemson.edu> hubcap@hubcap.clemson.edu (Mike Marshall) writes: struct hostent { char *h_name; /* official name of host */ char **h_aliases; /* alias list */ int h_addrtype; /* host address type */ int h_length; /* length of address */ char **h_addr_list; /* list of addresses from name server */ #define h_addr h_addr_list[0] /* address, for backward compatiblity */ }; In the above structure h_addr_list is a 4.3ism. One of the things that can end up here is an ordered list of MX hosts. Back in the pre DNS days of 4.2 all they did was look up an address in /etc/hosts and all that was needed was h_addr. Egad! No! It has nothing to do with MX records, it's just the realization that a single host can have multiple Internet addresses (ie multi-homed). rob -- william robertson rob@violet.berkeley.edu indecision is the key to flexiblity