From owner-freebsd-alpha Sun Nov 5 13:18:44 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from alcanet.com.au (unknown [203.62.196.10]) by hub.freebsd.org (Postfix) with SMTP id 9437337B4D7; Sun, 5 Nov 2000 13:18:39 -0800 (PST) Received: by border.alcanet.com.au id <115209>; Mon, 6 Nov 2000 09:17:53 +1100 Content-return: prohibited Date: Mon, 06 Nov 2000 08:18:23 +1100 From: Peter Jeremy Subject: Re: cvs commit: src/sys/boot/alpha/common main.c src/sys/boot/al To: Doug Rabson Cc: Mike Smith , alpha@FreeBSD.ORG Mail-followup-to: Doug Rabson , Mike Smith , alpha@FreeBSD.ORG Message-Id: <00Nov6.091753est.115209@border.alcanet.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Oct 27, 2000 at 10:28:38AM +0100, Doug Rabson wrote: >On Thu, 26 Oct 2000, Mike Smith wrote: >> Forgive the silly question, but is there any reason that boot1 doesn't >> read the load address from the loader object? > >On alpha, /boot/loader is just a binary (the headers have been stripped >off). When I wrote it, I didn't think I would be able to squeeze an ELF >loader into the space available. Currently there are 280 bytes spare - >probably not enough. Any reason why you couldn't have a primitive header: eg magic number and start address in /boot/loader. The code to read this and appropriately relocate /boot/loader shouldn't be too big. I agree that it's undesirable to wind up with yet another incompatible object format, but having an unbootable machine because /boot/loader expects a different load address to boot1 is even less desirable. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message