dnb@fltk.UUCP (David Buonomo) (12/13/89)
Does anyone know of a document (formal or informal) that would describe the differences/changes between Berkley 4.2 and 4.3. Thanks in advance. David Buonomo FileTek Rockville, Maryland (301) 984-1542
hubcap@hubcap.clemson.edu (Mike Marshall) (12/14/89)
I'm not qualified to talk about the implimentation differences, but one of
the functional differences between 4.2 and 4.3 networking can be seen in
/usr/include/netdb.h:
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.
-Mike hubcap@clemson.educliff@cpsc.ucalgary.ca (Cliff Marcellus) (12/15/89)
In article <301@fltk.UUCP>, dnb@fltk.UUCP (David Buonomo) writes: > Does anyone know of a document (formal or informal) that would describe the > differences/changes between Berkley 4.2 and 4.3. Thanks in advance. > Pick up a copy of "Bug Fixes and Changes in 4.3BSD" by M.K. McKusick, J.M. Bloom, and M.J. Karels 4.3BSD Doc. SMM:12 (of April 15, 1986) BTW : the 4.2BSD Doc set has a "Bug Fixes and Changes in 4.2BSD" if that might be of historical interest (0.5 :-)) Cliff -- Cliff Marcellus UUCP : {any backbone}!calgary!ssg-vax-a!cliff Dept of Physics and Astronomy DOMAIN : cliff@ssg-vax-a.phys.UCalgary.CA The University of Calgary SPAN : CANCAL::CLIFF OPINIONS WITHIN ARE MY OWN AND DO NOT REFLECT THOSE OF THE UNIVERSITY OF CALGARY
rob@violet.berkeley.edu (Rob Robertson) (12/17/89)
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