From owner-freebsd-hackers Mon Jul 19 11:54: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 5C97214F38 for ; Mon, 19 Jul 1999 11:54:05 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id EAA00964; Mon, 19 Jul 1999 04:50:50 -0700 Date: Mon, 19 Jul 1999 11:51:50 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Mike Smith Cc: "Daniel C. Sobral" , freebsd-hackers@FreeBSD.ORG Subject: Re: System unique identifier..... In-Reply-To: <199907191845.LAA00408@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > Mike Smith wrote: > > > > > > > > > > The loader will, at some stage in the future, grow a persistent data > > > > > store in which items like this can be saved. > > > > > > > > Doesn't /boot/[defaults/]loader.conf[.local] qualify as persistent > > > > data storage? > > > > > > There is little or no chance that the loader will gain the ability to > > > write back to filesystems. Some of them don't support it (eg. > > > iso9660), others may not (TFTP, NFS), and the code required for some of > > > them (especially UFS) would be problematically large. > > > > But that's okay. If the persistent storage is the loader conf files, they > > can be updated from single or multi-user mode. > > There are cases where they need to be updated _by_the_loader_; see eg. > the "nextboot" manpage for functionality that we have currently lost. So much the better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message