From owner-freebsd-hackers Mon May 27 16:21:20 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA07816 for hackers-outgoing; Mon, 27 May 1996 16:21:20 -0700 (PDT) Received: from perki.connect.com.au (perki.connect.com.au [192.189.54.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA07798 for ; Mon, 27 May 1996 16:21:17 -0700 (PDT) Received: (from uucp@localhost) by perki.connect.com.au id JAA10603 (8.7.5/IDA-1.6); Tue, 28 May 1996 09:21:04 +1000 (EST) >Received: from localhost (giles@localhost [127.0.0.1]) by nemeton.com.au (8.6.12/8.6.9) with SMTP id IAA15677; Tue, 28 May 1996 08:34:29 +1000 Message-Id: <199605272234.IAA15677@nemeton.com.au> To: Michael Smith cc: freebsd-hackers@freebsd.org Subject: Re: three stage boot again Date: Tue, 28 May 1996 08:34:28 +1000 From: Giles Lean Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 27 May 1996 15:17:14 +0930 (CST) Michael Smith wrote: > I think you're on the money here; the third stage shouldn't care how it > got into memory, it should be able to derive _everything_ by examining the > environment that it finds itself in on startup. > > (I know this means two bootp requests if it's come in from a netboot > environment, but that shouldn't hurt). NetBSD (just as an example :) will already make two bootp/RARP requests in a diskless environment to reduce the boot blocks <-> kernel interaction. Giles