From owner-freebsd-current Wed Apr 22 06:55:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA15057 for freebsd-current-outgoing; Wed, 22 Apr 1998 06:55:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley585.res.iastate.edu (friley585.res.iastate.edu [129.186.167.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA15037 for ; Wed, 22 Apr 1998 13:55:39 GMT (envelope-from ccsanady@friley585.res.iastate.edu) Received: from friley585.res.iastate.edu (loopback [127.0.0.1]) by friley585.res.iastate.edu (8.8.8/8.8.8) with ESMTP id IAA02372; Wed, 22 Apr 1998 08:54:46 -0500 (CDT) (envelope-from ccsanady@friley585.res.iastate.edu) Message-Id: <199804221354.IAA02372@friley585.res.iastate.edu> X-Mailer: exmh version 2.0.1 12/23/97 To: Peter Wemm cc: John-Mark Gurney , Terry Lambert , current@FreeBSD.ORG Subject: Re: ELF kernels: When? In-reply-to: Your message of "Wed, 22 Apr 1998 17:59:28 +0800." <199804220959.RAA05222@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 22 Apr 1998 08:54:45 -0500 From: Chris Csanady Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The real problems are: >- The bootblocks do not load the ELF symbol table, so DDB can't see it. >- DDB doesn't understand the ELF symbol tables yet anyway. >- the bootblocks have *zero* bytes free at present. There is ELF load code >available, but you have to disable BAD144 to get it to fit. Restructuring >the code so that the #ifdefs are not too messy tips the bootblocks over >the limit by a few bytes. >- The loader is quite simple, it pulls in the text and data LOAD sections, >without any of the section headers etc. Those section headers and string >tables are needed to do proper runtime linking via link_elf.c. So, does anyone know enough about bootblocks to look at integrating NetBSD's? They have done a significant amount of work in this area it seems, and they already have a two-stage design. Trying to squeeze every last bit out of the current blocks seems futile.. Are there any arguments against doing this? Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message