Darren Reed writes: > Note that I was referring to libnsl only, not libsocket. > In this instance, HP-UX doesn't have a libsocket, only libnsl.
Ah, ok. The original thread was about the combination of libsocket and libnsl, which are pretty much always used together. Still, libc on HP-UX has the libnsl interfaces as well: # nm /usr/lib/libc.2 | grep gethostbyname __gethostbyname_r | 291296|extern|code |$CODE$ _gethostbyname | 291880|extern|code |$CODE$ gethostbyname | 291816|extern|entry | gethostbyname | 291880|extern|code |$CODE$ > For some reason IRIX slipped under my radar...but I'm not at > all sure which versions of that require one or both of these > (I don't currently have any access to IRIX boxen.) Nor do I. A trip to the local museum is in order. ;-} > I would be interested to see a survey of System V Unixes to > see which still had libnsl/libsocket, when they transitioned (if > they have), etc. We've don't this before, and though I don't have the results at hand, I don't recall us finding any other system that segregates these functions the way Solaris does. > I'm curious to know if you're referal to "System V holdouts" is > more a reference to the existance of current/modern "System V" > unix as opposed to Linux/BSD (which seem to dominate a large > portion of the space today.) I'm referring to System V purists who apparently still think either that BSD sockets aren't the "real" networking interfaces, or that networking somehow is just an optional OS feature. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
