Alan Coopersmith writes: > Having spent more time fixing yet another open source package > to find the socket/name lookup functions on Solaris in libnsl > & libsocket that all other commonly used OS'es put in libc, I > have to wonder - is there any reason to keep them out of libc?
They're awful, aren't they? > Couldn't we fold them in and leave filters, as was done for the > thread libraries? Are the libxnet versions of the overlapping > functions incompatible, and even if so, can't we fix that in a > less painful way than forcing Solaris-ism's into every open source > project that wants to open a socket or find a hostname? Yes, they're incompatible -- for ancilary data at least, as well as some of the error returns. :-/ This has been discussed to death many times (networking-discuss is probably a better list for it; that's where the networking people who've discussed it before hang out), and we've threatened to do it before (I think meem was the last to discuss it seriously), but I don't think there's an open CR on it. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 35 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 opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
