Date: Tue, 18 Jun 1996 09:18:49 -0500 From: "Eric L. Hernes" <erich@lodgenet.com> To: "Jordan K. Hubbard" <jkh@time.cdrom.com> Cc: erich@FreeBSD.org, ports@FreeBSD.org Subject: Re: linux_lib port Message-ID: <199606181418.JAA17643@jake.lodgenet.com> In-Reply-To: Your message of "Tue, 18 Jun 1996 06:55:35 PDT." <199606181355.GAA07954@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606181418.JAA17643>