From owner-freebsd-current  Wed Dec 30 21:11:51 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA20719
          for freebsd-current-outgoing; Wed, 30 Dec 1998 21:11:51 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ix.netcom.com (sil-wa15-47.ix.netcom.com [207.93.148.47])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA20362
          for <current@FreeBSD.ORG>; Wed, 30 Dec 1998 21:09:29 -0800 (PST)
          (envelope-from tomdean@ix.netcom.com)
Received: (from tomdean@localhost)
	by ix.netcom.com (8.9.1/8.8.8) id VAA18502;
	Wed, 30 Dec 1998 21:05:39 -0800 (PST)
	(envelope-from tomdean)
Date: Wed, 30 Dec 1998 21:05:39 -0800 (PST)
Message-Id: <199812310505.VAA18502@ix.netcom.com>
From: Thomas Dean <tomdean@ix.netcom.com>
To: current@FreeBSD.ORG
Subject: Prospects for fixing aout-to-elf build?
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I have been watching this thread with interest.

I have an SMP system that I want to upgrade to ELF, when the process
appears to work.  This system is not a mission-critical one, but, I
would like to keep it working.  I have been dragging my feet, waiting
for ports, etc.

Will the aout-to-elf upgrade process be fixed?

tomdean

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message