From owner-freebsd-hackers  Thu Aug 21 13:38:07 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id NAA18057
          for hackers-outgoing; Thu, 21 Aug 1997 13:38:07 -0700 (PDT)
Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA18051
          for <hackers@FreeBSD.ORG>; Thu, 21 Aug 1997 13:38:05 -0700 (PDT)
Received: (from karpen@localhost)
	by ocean.campus.luth.se (8.8.5/8.8.5) id WAA15114;
	Thu, 21 Aug 1997 22:42:06 +0200 (CEST)
From: Mikael Karpberg <karpen@ocean.campus.luth.se>
Message-Id: <199708212042.WAA15114@ocean.campus.luth.se>
Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()]
In-Reply-To: <199708211612.JAA23531@phaeton.artisoft.com> from Terry Lambert at "Aug 21, 97 09:12:46 am"
To: terry@lambert.org (Terry Lambert)
Date: Thu, 21 Aug 1997 22:42:05 +0200 (CEST)
Cc: hackers@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL31H (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

According to Terry Lambert:
[... moving to ELF...]
> The LKM situation is equally grim; the LKM's must be switched at
> the same time.  This is because the LKM relocation is done by
> linking against the kernel symbol table.  Try linking an a.out
> image against the kernel symbol table.

Say, isn't that a good thing? I thought the current LKM scheme was disliked,
dysfunctional, and crippled in many ways. That's the impression I've gotten
from reading these lists for a while, at least. So if we now have to redo
them, that'd be a nice chance to get them right, and possibly compatible with
something soneone else uses, if it's good. No?

  /Mikael