From owner-freebsd-hackers Wed Jul 21 23:27: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles520.castles.com [208.214.165.84]) by hub.freebsd.org (Postfix) with ESMTP id C676C14BF4; Wed, 21 Jul 1999 23:26:54 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id XAA00979; Wed, 21 Jul 1999 23:22:04 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907220622.XAA00979@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrzej Bialecki Cc: "Brian F. Feldman" , "Daniel C. Sobral" , freebsd-hackers@FreeBSD.org Subject: Re: System unique identifier..... In-reply-to: Your message of "Wed, 21 Jul 1999 12:49:14 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 21 Jul 1999 23:22:04 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > That's not quite true. It wouldn't be too hard to modify existant files, > > but writing new ones/truncating would take a lot of work. It's still not > > a great idea to try to use a file on the FS for storage of persistent > > data. Wouldn't it be possible to have the kernel itself read in persistent > > data (in some form such as getenv?) to be written to disk? That way, the > > boot loader could pass it easily, and not have to worry about storage. > > This may sound like a heresy to you, but... Why don't use the Forth blocks > for that? For what? Saving parametric data? That was always the plan, but the last thing I think anyone wants to do is rewrite the ffs code in Forth. > They were invented for that purpose. We can create the files > beforehand (under normal OS operation), then from the bootloader we can > read and modify them - I suppose writing to a disk block is much easier > than through the filesystem layer... Yes, that's what we've always discussed as being the most likely course of action. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message