From owner-freebsd-current  Mon Apr 22 22:44:33 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id WAA06016
          for current-outgoing; Mon, 22 Apr 1996 22:44:33 -0700 (PDT)
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA06011
          for <freebsd-current@freebsd.org>; Mon, 22 Apr 1996 22:44:30 -0700 (PDT)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.5/8.6.9) id WAA19305; Mon, 22 Apr 1996 22:44:02 -0700 (PDT)
Date: Mon, 22 Apr 1996 22:44:02 -0700 (PDT)
Message-Id: <199604230544.WAA19305@silvia.HIP.Berkeley.EDU>
To: ivan@nauplius.rsmas.miami.edu
CC: freebsd-current@freebsd.org
In-reply-to: <199604221935.PAA08676@nauplius.rsmas.miami.edu> (message from Ivan Lima on Mon, 22 Apr 1996 15:35:11 -0400 (EDT))
Subject: Re: shared library
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

 * Where can I find shared libraries like libc.so.3.0?

If you are running -current, it's in /usr/lib.  ("/sbin/ldconfig -r"
will tell you where all the shared libraries are on your system.)

If you are not, and are trying to run the packages you picked up from
packages-current, just do an "ln -s libc.so.2.2 libc.so.3.0".  That
will probably work for most applications, the differences so far are
only a few deleted functions so running libc.so.3.0 binaries that way
won't cause any problems.

Note that everything you compile from now on will be linked to that
version of libc, and you can no longer give binaries to your friends
running 2.1R, for instance.  Also, the ports are tracking -current, so 
some of them will not work on 2.1R or -stable.

Satoshi