From owner-freebsd-current Wed Jun 30 12:10:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 3439814FE3 for ; Wed, 30 Jun 1999 12:10:09 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 803F182; Thu, 1 Jul 1999 03:10:08 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: "David E. Cross" Cc: Doug White , freebsd-current@FreeBSD.ORG Subject: Re: Upgrading from ancient to current... In-reply-to: Your message of "Wed, 30 Jun 1999 14:29:18 -0400." <199906301829.OAA80498@cs.rpi.edu> Date: Thu, 01 Jul 1999 03:10:08 +0800 From: Peter Wemm Message-Id: <19990630191008.803F182@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David E. Cross" wrote: > This is a bit of a tangent from the original post, but when did the FreeBSD > kernel start supporting ELF natively (not talking about Linux emulation). > I made the mistake of attempting to run a 3.0 ELF world with a 2.2.5 > kernel, and it worked (mostly). I was unaware that anything that "old" > supported ELF. 2.2 supported ELF quite some time before 2.2-stable was branched, for almost as long as ELF binaries were supported under Linux emulation... Native ELF support was added nearly for free. The main thing that'll break is that 3.x kernels and libraries have syscalls that do not exist in 2.x and you'll get SIGSYS's etc. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message