From owner-freebsd-current Tue Jan 26 03:21:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA17333 for freebsd-current-outgoing; Tue, 26 Jan 1999 03:21:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA17326 for ; Tue, 26 Jan 1999 03:21:01 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id MAA04556; Tue, 26 Jan 1999 12:20:51 +0100 (CET) (envelope-from des) To: Brian Feldman Cc: Dag-Erling Smorgrav , Boris Staeblow , dillon@apollo.backplane.com, freebsd-current@FreeBSD.ORG Subject: Re: Heads up! New swapper and VM changes have been committed to -4.x References: From: Dag-Erling Smorgrav Date: 26 Jan 1999 12:20:49 +0100 In-Reply-To: Brian Feldman's message of "Mon, 25 Jan 1999 18:55:40 -0500 (EST)" Message-ID: Lines: 20 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman writes: > On 24 Jan 1999, Dag-Erling Smorgrav wrote: > > [...] > > These are statically linked, and must be relinked after libkvm has > > been rebuilt. > > [...] > > These are dynamically linked, and will automatically pick up the new > > libkvm. > But (most) still require the structures to be the exact same way, > which is the reason for the recompile anyway... don't forget that! No, because the libkvm interface has not changed, only its internals. libkvm must be updated to be able to talk to the kernel, and applications which use it must be relinked with it. In the case of dynamically linked applications, this is done automatically at load time. Or am I reading this wrong? DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message