From owner-freebsd-hackers Thu Oct 8 09:36:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA28989 for freebsd-hackers-outgoing; Thu, 8 Oct 1998 09:36:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from friley-185-114.res.iastate.edu (friley-185-114.res.iastate.edu [129.186.185.114]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA28973 for ; Thu, 8 Oct 1998 09:36:30 -0700 (PDT) (envelope-from ccsanady@friley-185-114.res.iastate.edu) Received: from friley-185-114.res.iastate.edu (loopback [127.0.0.1]) by friley-185-114.res.iastate.edu (8.9.1/8.9.1) with ESMTP id LAA00404 for ; Thu, 8 Oct 1998 11:36:24 -0500 (CDT) (envelope-from ccsanady@friley-185-114.res.iastate.edu) Message-Id: <199810081636.LAA00404@friley-185-114.res.iastate.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-hackers@FreeBSD.ORG Subject: new bootloader suggestions.. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 08 Oct 1998 11:36:24 -0500 From: Chris Csanady Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was wondering if we could make the environment of the new boot loader non-volatile. It seems as though variables that you set at boot should stick around. Could we possibly have a /boot/environment or something similar where the variables are actually written back? Although it is nice to support script type files, for most usage I would rather have the typical console like behavior. Chris Csanady To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message