Return to BSD News archive
Xref: sserve comp.os.linux:9909 comp.unix.bsd:4974 Path: sserve!manuel!munnari.oz.au!uunet!spool.mu.edu!yale.edu!ira.uka.de!math.fu-berlin.de!unidui!du9ds3!veit From: veit@du9ds3.uni-duisburg.de (Holger Veit) Newsgroups: comp.os.linux,comp.unix.bsd Subject: Re: Shared libraries - info for 386BSD porting wanted Date: 12 Sep 92 10:23:27 GMT Organization: Uni-Duisburg FB9 Datenverarbeitung Lines: 35 Message-ID: <veit.716293407@du9ds3> References: <peter.716225737@hilly> Reply-To: veit@du9ds3.uni-duisburg.de NNTP-Posting-Host: du9ds3.uni-duisburg.de Keywords: shared 386bsd In <peter.716225737@hilly> peter@micromuse.co.uk (Peter Galbavy) writes: >Hi, >Due to no response in the bsd group a couple of weeks ago, and the fact >I recently noticed that linux seems to have shared libraries I was >wondering if whoever knows *lots* about them can either (a) try to port >them or (b) help me port the implementaion across. >I realise that this will not be a trivial operation, but it is a starting >point. >At minimum, will someone tell me the "minimum working set" of linux source >files needed to understand how they are implemented. I take it there are >bits in exec() somewhere ? and the linker etc... >Thanks from a frustrated laptop owner without X386 due to lack of disk >space, >-- >Peter Galbavy >Tech Support, Micromuse Ltd >Phone: +44 71 352 7774 E-Mail: P.Galbavy@micromuse.co.uk Another thread has been just started about that. Don't look at the Linux sources, the type of implementation is for a hacker's OS ;-), but not for the future. Linux uses (as most SysV systems) fixed addresses for shared libraries, which is, with one simple word *unacceptable*. Holger -- | | / Dr. Holger Veit | INTERNET: veit@du9ds3.uni-duisburg.de |__| / University of Duisburg | BITNET: veit%du9ds3.uni-duisburg.de@UNIDO | | / Dept. of Electr. Eng. | "No, my programs are not BUGGY, these are | |/ Inst. f. Dataprocessing | just unexpected FEATURES"