Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!rutgers!mit-eddie!uw-beaver!milton!sumax!polari!rwing!pat
From: pat@rwing.UUCP (Pat Myrto)
Newsgroups: comp.unix.internals
Subject: Shared Lib Question (ISC)
Keywords: ISC i386 shared libraries
Message-ID: <276@rwing.UUCP>
Date: 5 May 91 20:28:09 GMT
Organization: Totally Unorganized
Lines: 25

I have noticed with interest the discussion going on regarding shared
libraries.  However, what is obvious is that there are several kinds
of shared libaries, all using some different scheme to operate.

Does anyone out there know how the type that is used on the ISC SysV
R3 version operate?  Does the whole image load into core and remain
there, and the programs that use the shared libary access the
functions they need?  Or does an attempt to load the library occur and
the system finds its allready loaded and shares the text, similar to
the way separate processes of the same program share text?  Once
loaded by a program using it, does it STAY in core, or do parts stay,
or if nothing is running that uses it, is the core space freed?

If the questions seem stupid, its because I have NO IDEA of how this
works - docs not being much help - so other than the obvious saving on
disk space, I am not really able to make an intelligent decision on
whether a given application would be best built with or without using
the shared library.

Thanks for any info...
-- 
pat@rwing                                       (Pat Myrto),  Seattle, WA
                            ...!uunet!pilchuck!rwing!pat
      ...!uw-beaver!uw-entropy!dataio!/
WISDOM:    "Travelling unarmed is like boating without a life jacket"