From owner-freebsd-hackers Sat Jan 3 13:28:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA04417 for hackers-outgoing; Sat, 3 Jan 1998 13:28:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from critic.cynic.net (critic.cynic.net [198.73.220.9]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA04413 for ; Sat, 3 Jan 1998 13:28:14 -0800 (PST) (envelope-from cjs@portal.ca) Received: from localhost (localhost [[UNIX: localhost]]) by critic.cynic.net (8.8.8/8.8.8) with SMTP id NAA15054; Sat, 3 Jan 1998 13:26:10 -0800 (PST) X-Authentication-Warning: critic.cynic.net: cjs owned process doing -bs Date: Sat, 3 Jan 1998 13:26:09 -0800 (PST) From: Curt Sampson X-Sender: cjs@critic.cynic.net To: Ollivier Robert cc: hackers@FreeBSD.ORG Subject: Re: FreeBSD ELF status? In-Reply-To: <19980101164804.30732@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk On Thu, 1 Jan 1998, Ollivier Robert wrote: > Considering the boot blocks size issue, it is more of an all or nothing > thing because if we want to boot our shiny new kernel, we need the new > boot blocks. If someone can do the Mithical 3-Stage Bootblock, it would > be easier (no I'm not volunteering :-)). Actually, the easiest solution to this sort of thing is to follow what many other systems (sun, alpha, etc.) do and have your basic boot blocks load in a file containing the second-stage bootstrap from the root filesystem. (Usually you have a utility called "installboot" which programs the block numbers of this file into the first-stage bootstrap.) Then you can have a boot program that's essentially as long and complex as you need. (NetBSD/i386 recently changed to doing things this way.) cjs Curt Sampson cjs@portal.ca Info at http://www.portal.ca/ Internet Portal Services, Inc. Through infinite mist, software reverberates Vancouver, BC (604) 257-9400 In code possess'd of invisible folly.