*BSD News Article 23978


Return to BSD News archive

Xref: sserve comp.os.linux.help:8882 comp.os.386bsd.questions:6883
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!news.umbc.edu!europa.eng.gtefsd.com!gatech!prism!gt8134b
From: gt8134b@prism.gatech.EDU (Robert Sanders)
Newsgroups: comp.os.linux.help,comp.os.386bsd.questions
Subject: Re: SUMMARY: FreeBSD vs. Linux
Message-ID: <123592@hydra.gatech.EDU>
Date: 15 Nov 93 18:39:24 GMT
References: <2btv9t$4nb@news.cs.tulane.edu> <2bui0j$blb@fw.novatel.ca> <2butta$jqc@news.cs.tulane.edu> <CGFCr0.F84@boulder.parcplace.com>
Followup-To: comp.os.linux.help
Organization: Georgia Institute of Technology
Lines: 40

In <CGFCr0.F84@boulder.parcplace.com> imp@boulder.parcplace.com (Warner Losh) writes:

>In article <2butta$jqc@news.cs.tulane.edu> cajho@uno.edu writes:
>>Sun-OS binaries?  Please elaborate...will this allow access to much commercial
>>software?

>If you have a Sun to run them on.

Well, I think any 68k machine will do for Sun3 binaries.  Some old
HPs300 machines would do the trick, I imagine, as would Amigas and
Macs.

>>Real shared libraries?  How are Linux's unreal?  What is the diff. between the
>>*BSD libs and Linux's libs?

>Linux's current shared libraries are a kludge.  Plain and simple.
>They require the developer keep jump tables around, or pure copies of
>the last release, niether of which is, IMHO, reasonable.  The tools
>are a kludge and require you to build the library twice often times.
>ELF support is coming, and will make Linux's shared more real.  I had

The end result is functionally the same; it just costs the developer
more and the user less.  I don't mind making the developer pay a 
little for extra speed and smaller size, but that's just me.
Admittedly, ELF libraries are much "cleaner" conceptually.

>The *BSD shared library support that I've seen is much more dynamic.
>It looks up things at runtime, which is what you want in a shared
>library implementation.  They are basically SunOS style shared

Which is what the developer wants in a shared library implementation.
It costs you much more at runtime.  As for SunOS-style being the
ultimate, ever notice how SunOS shared-library binaries take much
longer to fork() than statically linked binaries?  Hmm...

-- 
 _g,  '96 --->>>>>>>>>>   gt8134b@prism.gatech.edu  <<<<<<<<<---  CompSci  ,g_
W@@@W__        |-\      ^        | disclaimer:  <---> "Bow before ZOD!" __W@@@W
W@@@@**~~~'  ro|-<ert s/_\ nders |   who am I???  ^  from Superman  '~~~**@@@@W
`*MV' hi,ocie! |-/ad! /   \ss!!  | ooga ooga!!    |    II (cool)!         `VW*'