Return to BSD News archive
Newsgroups: comp.os.386bsd.misc
Path: sserve!newshost.anu.edu.au!munnari.oz.au!cs.mu.OZ.AU!bevan
From: bevan@mame.mu.OZ.AU (Bevan Anderson)
Subject: Re: how *not* to use shared libraries
Message-ID: <bevan.760686753@sungear>
Sender: news@cs.mu.OZ.AU
Organization: Computer Science, University of Melbourne, Australia
References: <2iuku1$sjs@dingo.cc.uq.oz.au>
Date: Tue, 8 Feb 1994 05:52:33 GMT
Lines: 35
Danny Thomas <D.Thomas@vthrc.uq.edu.au> writes:
>In comp.risks 15.41 Andrew Shapiro writes:
>> The other evening I stumbled upon an interesting single point failure
>for
>> Sun Microsystem computers. While working I distroyed the
>/lib/libc.so.0.15
>> file. To my surprise nothing works without it. I already knew that
>Sun's
>> defaulted to dynamic binding at link time, I also knew that it was
>possible
>> to suppress this option by using the -Bstatic keyword to the link
>editor,
>> ld(1). What surprised me was that the static option had not been used
>when
>> building any of the user commands. I would have expected some of the
>most
>> basic commands like ls, cp, and either tar or dd to be compiled with
>static
>> linking. If this were the case repairing the /lib/libc.so.0.15 file
>would
>doesn't say what version of SunOS he was using and whether it was fixed
>in later releases.
Its the same for all BSD derived SunOS's (after 3.5). The only statically
linked commands are in /sbin and /usr/bin/rcp ( so you can rcp in another
libc.so form another sun)..
Bevan..
--
Bevan Anderson.
bevan@mame.mu.OZ.AU | Phone +61 3 481 5764 ..{{ _____ __o Live Fast
bevan@ee.mu.OZ.AU | Work +61 3 344 6721 ...{ _____ _\<, Hit Hard
bevan@ecr.mu.OZ.AU | Fax +61 3 349 2182 ...{{ ----- (*)'(*) Die Young