From owner-freebsd-current  Tue Apr  1 08:27:31 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id IAA10239
          for current-outgoing; Tue, 1 Apr 1997 08:27:31 -0800 (PST)
Received: from austin.polstra.com (austin.polstra.com [206.213.73.10])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA10229
          for <current@FreeBSD.ORG>; Tue, 1 Apr 1997 08:27:26 -0800 (PST)
Received: from austin.polstra.com (jdp@localhost)
	by austin.polstra.com (8.8.5/8.8.5) with ESMTP id IAA01496;
	Tue, 1 Apr 1997 08:27:02 -0800 (PST)
Message-Id: <199704011627.IAA01496@austin.polstra.com>
To: Doug Rabson <dfr@nlsystems.com>
cc: phk@critter.dk.tfs.com, current@FreeBSD.ORG
Subject: Re: A new Kernel Module System 
In-reply-to: Your message of "Tue, 01 Apr 1997 09:31:02 +0100."
             <Pine.BSF.3.95q.970401092941.305A-100000@kipper.nlsystems.com> 
References: <Pine.BSF.3.95q.970401092941.305A-100000@kipper.nlsystems.com> 
Date: Tue, 01 Apr 1997 08:27:02 -0800
From: John Polstra <jdp@polstra.com>
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> Exactly what I was thinking.  PIC has no benefits for the kernel.
> The only thing I would need from the a.out shlib format is the
> relocations and runtime symbol table.

I don't think you can get a runtime symbol table, unless you're building
a shared object, i.e., using PIC.  You'll have to use the "normal"
symbol table.  That shouldn't be a problem as far as I can see.
--
   John Polstra                                       jdp@polstra.com
   John D. Polstra & Co., Inc.                Seattle, Washington USA
   "Self-knowledge is always bad news."                 -- John Barth