From owner-freebsd-hackers Mon Feb 9 17:49:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA14231 for hackers-outgoing; Mon, 9 Feb 1998 17:49:00 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA14220 for ; Mon, 9 Feb 1998 17:48:49 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id RAA06071; Mon, 9 Feb 1998 17:47:24 -0800 (PST) Message-Id: <199802100147.RAA06071@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: ade@demon.net cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: boot floppy banner In-reply-to: Your message of "Sat, 07 Feb 1998 16:56:52 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 09 Feb 1998 17:47:23 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith writes: > > > >What has to happen is that someone has to write the third-stage > >bootstrap. The biosboot code will shrink substantially when this > >happens. > > Ok. Forgive my ignorance in any of the below comments - I probably > need to hit myself over the head with a clue-by-four as far as > i386 booting goes.. :) Feh. There is only one place to start. > AIUI, with the two-stage boot process at the moment (MBR and biosboot), > the i386 validates the contents of the first few sectors of the disk, > loads in biosboot at some low memory location, Almost. Loads boot1, executes. Boot2 locates & loads boot2. > this code runs, prints > up the boot prompt, determines the kernel image to load, blits it in > at the 1Mb region, and passes control over and away we go. As far > as the end user is concerned, they can either sit and do nothing, > or type one line of text to load a different kernel.. > > Splitting this into three stage process: > > 1. MBR loads biosboot at > 2. biosboot runs and prompts > "where do you want to load the next boot program?" > 3. biosboot loads at > 4. runs and prompts > "which kernel do you want to load?" > 5. loads at 1Mb > 6. kernel runs.. > > Assuming I haven't messed up anywhere above :), I don't see where > the code shrinkage comes from.. biosboot still needs BAD144 etc.. > to be able to load the 3rd stage boot, and we still want to give > the pilot a choice as to where this code is loaded from.. All the code for parsing kernel options goes. The code for loading the kernel is simplified. The splash code goes. The VESA code goes. The NEXTBOOT code goes. The protected mode/real mode switch code may be simplified (depending on where boot3 is actually loaded). More importantly, adding more features doesn't involve more boot2 bloat. (Sorry for the delay here). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe hackers" in the body of the message