From owner-freebsd-hackers Mon Jan 23 23:37:24 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id XAA19119 for hackers-outgoing; Mon, 23 Jan 1995 23:37:24 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id XAA19113 for ; Mon, 23 Jan 1995 23:37:15 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id SAA12857; Tue, 24 Jan 1995 18:32:36 +1100 Date: Tue, 24 Jan 1995 18:32:36 +1100 From: Bruce Evans Message-Id: <199501240732.SAA12857@godzilla.zeta.org.au> To: julian@tfs.com, peter@bonkers.taronga.com Subject: Re: writing bootcode; need a method Cc: hackers@FreeBSD.org, mmead@goof.com, terry@cs.weber.edu Sender: hackers-owner@FreeBSD.org Precedence: bulk >well if we are going to correct things, it's like this: >> > ,------------------------.----------------. >> > | 4 | 5 ... | >> > |---.---.---. | | >> > | 1 | 2 | 3 | | | >> > `---'---'---'------------'----------------' >> > 1) BSD second stage boot. (loads label and 3rd stage) >> > 2) BSD disklabel. >> > 3) BSD Third stage boot. (loads kernel) >> > 4) BSD slice 'a'. >> > 5) BSD subsequent slices. I usually call 1) and 3) the first stage boot. We need a stage after that soon. I want it to be in /kernel0. There is also 6) BSD bad144 table at the end of what the disklabel and/or the drivers say is the end of the disk (the wrong place). On "i386" systems there are also the DOSpartitions, which can be laid out as something between a ternary and a quaternary tree and can have slightly complicated overlaps with each other and very complicated/ incoherent overlaps with the BSD partitions, especially on misconfigured systems. [Picture omitted due to lack of time, space and drawing capabilities.] Bruce