From owner-freebsd-hackers Tue Apr 22 19:53:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA28480 for hackers-outgoing; Tue, 22 Apr 1997 19:53:33 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA28473 for ; Tue, 22 Apr 1997 19:53:30 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id MAA18859; Wed, 23 Apr 1997 12:23:18 +0930 (CST) From: Michael Smith Message-Id: <199704230253.MAA18859@genesis.atrad.adelaide.edu.au> Subject: Re: additional boot stage? In-Reply-To: from Jaye Mathisen at "Apr 22, 97 04:35:39 pm" To: mrcpu@cdsnet.net (Jaye Mathisen) Date: Wed, 23 Apr 1997 12:23:17 +0930 (CST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jaye Mathisen stands accused of saying: > > Something I was was thinking would be useful is to have a kernel boot > path, or list of bootable kernels, or some mechanism such that if /kernel > doesn't boot, /kernel.bak boots or some fallback mechanism. NetBSD does this. > I was thinking it could be handled if /kernel loaded and tracked the > bootedness or non-bootedness of the next kernel, it would be handy, w/o > having to write/rewrite the bootblocks, which makes me nervous. > > Or something. It would be nice. The guys at Whistle have done this already; start with 'man nextboot'. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[