[ksh93-integration-discuss] Re: [ast-users] /dev/tcp+/dev/udpnotcompiled-in for Solaris ksh93r...

[Roland Mainz]

Casper.Dik at Sun.COM wrote:
> >Some questions (CC:'ing Casper to have a look at the problem, too):
> >- AFAIK none of { Xorg, Xsun, Mozilla. FireFox, KDE, Kerberos5, bash }
> >uses libxnet... the question is: Why can't they use libxnet ?
> 
> One of the biggest issue by folding the socket/nsl libraries, regardless
> of libxnet, is the huge pile of .data and .bss contained in libnsl:
> 
> % size /lib/linsl.so
> 575446 + 33881 + 22251 = 631578
> 
> Huge.

Yes... but you know the "cure" for this problem... :-)
1. Compile libnsl with -xstrconst
2. Hunt-down the remaining non-|const| data manually...

> >- The majority of applications in OS/Net uses libnsl+libsocket and not
> >libxnet (182 vs. 16) - is that just historical cruft that they do not
> >use libxnet (sometimes all three libraries are used (like
> >http://cvs.opensolaris.org/source/xref/on/usr/src/cmd/cmd-inet/usr.sbin/ping/Makefile#43))
> >?
> 
> libxnet requires some different compilation; for the most part they
> are different wrappers around the same syscalls.
> 
> When functions are made standard compliant they are sometimes generalized;
> that's why they're not fully compatible (different argument types:
> see sendmsg/recvmsg).
> 
> Also you must note that libxnet is not a proper library; it's
> a filter; it does not contain actual code but rather a view
> on libsocket/libnsl/libc

I think the best we can do right now is to keep the current status and
don't switch to libxnet...

----

Bye,
Roland

-- 
  __ .  . __
 (o.\ \/ /.o) roland.mainz at nrubsig.org
  \__\/\/__/  MPEG specialist, C&&JAVA&&Sun&&Unix programmer
  /O /==\ O\  TEL +49 641 7950090
 (;O/ \/ \O;)