From owner-freebsd-current Fri Jan 15 12:06:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA04296 for freebsd-current-outgoing; Fri, 15 Jan 1999 12:06:21 -0800 (PST) (envelope-from owner-freebsd-current@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 MAA04291 for ; Fri, 15 Jan 1999 12:06:19 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA02063; Fri, 15 Jan 1999 11:57:11 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901151957.LAA02063@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Feldman cc: Mike Smith , Poul-Henning Kamp , Jaye Mathisen , current@FreeBSD.ORG Subject: Re: Can the bootloader create a file or set a flag in the bootblocks? In-reply-to: Your message of "Fri, 15 Jan 1999 14:56:54 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 15 Jan 1999 11:57:11 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, 15 Jan 1999, Mike Smith wrote: > > Obviously we can't write to CDROMs, but a persistence mechanism needs > > to work with each of these others. I've been leaning towards a very > > simple solution using a small, preallocated file which we just > > overwrite. It's not beautiful, but it's workable. > > It can't go into free space in a boot block? We still have room left over... > It could only be a few bytes, enumerating numbered kernels in /boot/kernels.rc, > or something like that It needs to be a general solution, and see above, again, for the things it needs to be able to do. -- \\ 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 freebsd-current" in the body of the message