Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!spool.mu.edu!uunet!mcsun!uknet!pavo.csi.cam.ac.uk!camcus!jp107 From: jp107@cus.cam.ac.uk (Jon Peatfield) Newsgroups: comp.unix.bsd Subject: Re: Shared Libs for X11?, was Re: 386bsd -- The New Newsgroup Message-ID: <JP107.92Sep18105432@grus.cus.cam.ac.uk> Date: 18 Sep 92 09:54:35 GMT References: <veit.716291291@du9ds3>> <1992Sep14.232949.9093@bby.com.au> <2aFn02vQ22Jx01@JUTS.ccc.amdahl.com> <Buo74w.Jp2@pix.com> Sender: news@infodev.cam.ac.uk (USENET news) Organization: U of Cambridge, England Lines: 22 In-Reply-To: stripes@pix.com's message of 16 Sep 92 12:10:07 GMT Nntp-Posting-Host: grus.cus.cam.ac.uk In <Buo74w.Jp2@pix.com> stripes@pix.com (Josh Osborne) correctly states: > Runtime linked code will not allways be the same for each copy of the > same executable. Not if we support a library path like Sun does (which > is a good idea), or if a new lib is installed after starting one copy of > xterm but before another is started. But, by being careful one can arrange to keep all the parts of the program which must be modified in the data segment of the program, thus allowing the text segment to remain shared and unmodified after final linkage. Thus while the data segment is a bit bigger, and unsharable most of the program is sharable and can be loaded r/o into memory. LD_LIBRARY_PATH or equivalent is too good a thing to loose. Look at the hash that HP made of shared libs... -- Jon -- Jon Peatfield, Computer Officer, the DAMTP, University of Cambridge Telephone: (+44 223) 33-7852 Mail: J.S.Peatfield@amtp.cam.ac.uk I'm an international arms dealer. You can be one too. Ask me how!