From owner-freebsd-hackers Mon Mar 15 0:42: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freja.webgiro.com (10.0.29.209.212.in-addr.arpa [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 401C614DA8; Mon, 15 Mar 1999 00:41:58 -0800 (PST) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 2268C18C3; Mon, 15 Mar 1999 09:41:49 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 1B3D04992; Mon, 15 Mar 1999 09:41:49 +0100 (CET) Date: Mon, 15 Mar 1999 09:41:47 +0100 (CET) From: Andrzej Bialecki To: Ruslan Ermilov Cc: sheldonh@FreeBSD.ORG, FreeBSD Hackers Subject: Re: kern/9670: kernel config at boot time via -c gives save option but looses settings In-Reply-To: <19990315093043.A64525@relay.ucb.crimea.ua> 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 On Mon, 15 Mar 1999, Ruslan Ermilov wrote: > I just worried about ERRATA - it is incorrect!!! > `boot -c' changes are not written into /kernel.config. > > In 2.2.8 boot2 worried about reading /kernel.config, > and dset worried about writing /kernel.config. Ehm, not quite. boot2 in 2.2.8 read the boot.conf which was just the boot flags. The actual changes from UserConfig were being extracted and written out as binary patches to the kernel (can you say "ugly"?). Or, alternatively, you could write them manually into /kernel.config, and they would be automatically read by /kernel, whether you wanted it or not. Now, boot2 reads about the same info, but from /boot/boot.conf, but if you don't load /kernel.config explicitely, /kernel ignores it. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message