From owner-freebsd-current Fri Jan 15 09:45:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14349 for freebsd-current-outgoing; Fri, 15 Jan 1999 09:45:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from schizo.cdsnet.net (schizo.cdsnet.net [204.118.244.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14340 for ; Fri, 15 Jan 1999 09:45:24 -0800 (PST) (envelope-from mrcpu@internetcds.com) Received: from localhost (mrcpu@localhost) by schizo.cdsnet.net (8.8.8/8.7.3) with SMTP id JAA15675 for ; Fri, 15 Jan 1999 09:40:57 -0800 (PST) Date: Fri, 15 Jan 1999 09:40:57 -0800 (PST) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: current@FreeBSD.ORG Subject: Can the bootloader create a file or set a flag in the bootblocks? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It would be kind of cool if when managing a remote system if /kernel failed to boot, then on the next boot, the loader will fire up /kernel.old, or a /kernel.somethingorother. Sort of a kernel-clean flag. Then 300 miles away, I can try stuff, and have at least some assurance that I'll eventually be able to get back to a kernel I could use. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message