Casper.Dik at Sun.COM wrote:
> >> solaris is still in the 70's on this one
> 
> 70s?  Sockets?  It's an AT&T thing.

You mean the libsocket/libnsl invention is from SysV or what ?

> >Well, maybe one argument could be that most small applications do not
> >need networking... but I do not know the exact argumentation.
> >Maybe Casper Dik can explain why libsocket/libnsl were not integrated
> >into libc yet (other stuff such as threading support was integrated for
> >Solaris 10 - why didn't that happen with networking, too ?) ...
> 
> Perhaps this explains it: (size)
> /lib/libc.so.1: 874985 + 28302 + 5750 = 909037
> /lib/libsocket.so.1: 43370 + 4269 + 843 = 48482
> /lib/libnsl.so.1: 577086 + 33945 + 22291 = 633322
> 
> Libnsl is a *pig*.  Especially the 60K of *data* it apparently needs
> per process.

How much reduction do you get when libnsl gets recompiled with
-xstrconst ? IMO this could be a huge chunk just coming from the string
literals which are read/write in Sun Workshop/Forte/Studio instead of
read-only.

----

Bye,
Roland

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

Reply via email to