From owner-freebsd-current Sat Mar 16 17:31:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA12952 for current-outgoing; Sat, 16 Mar 1996 17:31:24 -0800 (PST) Received: from perki.connect.com.au (perki.connect.com.au [192.189.54.5]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA12947 Sat, 16 Mar 1996 17:31:21 -0800 (PST) Received: (from uucp@localhost) by perki.connect.com.au id MAA03457 (8.6.12/IDA-1.6); Sun, 17 Mar 1996 12:31:04 +1100 >Received: from localhost (giles@localhost [127.0.0.1]) by nemeton.com.au (8.6.12/8.6.9) with SMTP id KAA18811; Sun, 17 Mar 1996 10:12:11 +1100 Message-Id: <199603162312.KAA18811@nemeton.com.au> To: Andreas Klemm cc: sos@freebsd.org, David Langford , current@freebsd.org Subject: Re: Native & Linux ELF support finally there... In-reply-to: Date: Sun, 17 Mar 1996 10:12:10 +1100 From: Giles Lean Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 16 Mar 1996 11:11:51 +0100 (MET) Andreas Klemm wrote: > ELF format has become "industry standard". Every Unix Vendor, who > migrated his OS to SVR4, has done the final step to ELF format. > HP, Silicon Graphics, Sun, ... HP-UX isn't SysVr4. Neither does did it use ELF last time I looked but instead (like us) an enhanced a.out format to support shared libraries. While ELF is nicer to consider migrating we'd need to be sure that the migration path is very smooth and that the maintenance overhead of supporting a.out for backward compatibility would not be burdensome. Giles