From owner-freebsd-hackers  Fri Aug  9 07:52:10 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id HAA17221
          for hackers-outgoing; Fri, 9 Aug 1996 07:52:10 -0700 (PDT)
Received: from scruz.net (nic.scruz.net [165.227.1.2])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA17211
          for <hackers@FreeBSD.ORG>; Fri, 9 Aug 1996 07:52:07 -0700 (PDT)
Received: from osprey.grizzly.com by scruz.net (8.7.3/1.34)
	id HAA03785; Fri, 9 Aug 1996 07:52:04 -0700 (PDT)
Received: (from markd@localhost) by osprey.grizzly.com (8.7.5/8.7.3) id HAA22659; Fri, 9 Aug 1996 07:52:28 -0700 (PDT)
Date: Fri, 9 Aug 1996 07:52:28 -0700 (PDT)
Message-Id: <199608091452.HAA22659@osprey.grizzly.com>
From: Mark Diekhans <markd@Grizzly.COM>
To: lada@ws2301.gud.siemens.co.at
CC: hackers@FreeBSD.ORG
In-reply-to: <199608090817.AA074198640@ws2301.gud.siemens.co.at>
	(lada@ws2301.gud.siemens.co.at)
Subject: Re: What are the plans for ELF support?
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>What for?  Is there something that the half-assed[1] GNU ELF support gains
>you that the a.out libraries don't have (remember: we're not Linux, a.out
>libs are really dynamically--read PIC--linked)?

Mostly upgrade of GNU devsys pieces...

But this question came up when I discovered a missing feature in the 
current dynamic loading that I was contemplating adding.

I certainly wouldn't want to go though the amount of instability the Linux
people did for a file format change.