From owner-freebsd-hackers Tue Apr 22 16:35:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA16315 for hackers-outgoing; Tue, 22 Apr 1997 16:35:44 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA16308 for ; Tue, 22 Apr 1997 16:35:40 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.5/8.7.3) with SMTP id QAA19617 for ; Tue, 22 Apr 1997 16:35:39 -0700 (PDT) Date: Tue, 22 Apr 1997 16:35:39 -0700 (PDT) From: Jaye Mathisen To: hackers@freebsd.org Subject: additional boot stage? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Occasionally, it seems I'm having to work on machines that aren't close, and need a bit of kernel tweaking now and then... 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. 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.