From owner-freebsd-ports  Tue Jun 18 07:20:27 1996
Return-Path: owner-ports
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id HAA28708
          for ports-outgoing; Tue, 18 Jun 1996 07:20:27 -0700 (PDT)
Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA28703;
          Tue, 18 Jun 1996 07:20:23 -0700 (PDT)
Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id JAA24949; Tue, 18 Jun 1996 09:20:05 -0500
Received: from garbo.lodgenet.com(204.124.123.250) by bacall via smap (V1.3)
	id sma024940; Tue Jun 18 09:19:56 1996
Received: from jake.lodgenet.com (jake.lodgenet.com [204.124.120.30]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id JAA23845; Tue, 18 Jun 1996 09:19:58 -0500
Received: from localhost (localhost [127.0.0.1]) by jake.lodgenet.com (8.7.5/8.6.12) with SMTP id JAA17643; Tue, 18 Jun 1996 09:18:49 -0500 (CDT)
Message-Id: <199606181418.JAA17643@jake.lodgenet.com>
X-Authentication-Warning: jake.lodgenet.com: Host localhost [127.0.0.1] didn't use HELO protocol
X-Mailer: exmh version 1.6.2 7/18/95
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
cc: erich@FreeBSD.org, ports@FreeBSD.org
Subject: Re: linux_lib port 
In-reply-to: Your message of "Tue, 18 Jun 1996 06:55:35 PDT."
             <199606181355.GAA07954@time.cdrom.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 18 Jun 1996 09:18:49 -0500
From: "Eric L. Hernes" <erich@lodgenet.com>
Sender: owner-ports@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

"Jordan K. Hubbard" writes:
>Wouldn't it be better to have it run the linux ldconfig automatically
>somehow (or at least tell the user how to do it) - most people aren't going
>to think to build the ld cache in /compat/linux/etc by running
>/compat/linux/sbin/ldconfig, I think.

I thought I'd run it before tarballing up the collection next time, then
the cache is just there.  I wasn't thinking straight when I
rm'ed it before :(.

Yes, we could run ldconfig automatically, but originally, you could
install the libs and not have the kernel support, so the ldconfig would
fail.  Now I believe that there's always at least enough kernel support
to run the lkm (right?).  So we could run something like
/compat/linux/sbin/ldconfig || (/usr/bin/linux && /compat/linux/sbin/ldconfig)'
right?  Are there any advantages over just supplying a cache? probably
preserving any other libs that were there before.

>
>					Jordan
>
eric.
--
erich@lodgenet.com
http://rrnet.com/~erich erich@rrnet.com