From owner-freebsd-questions Mon Apr 3 11:46:10 2000 Delivered-To: freebsd-questions@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id BA74537B5BE for ; Mon, 3 Apr 2000 11:46:06 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from slave (doug@slave [10.0.0.1]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id LAA02365; Mon, 3 Apr 2000 11:45:49 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Mon, 3 Apr 2000 11:45:49 -0700 (PDT) From: Doug Barton X-Sender: doug@dt051n0b.san.rr.com To: Richard Brooksby Cc: freebsd-questions@freebsd.org, Ravenbrook System Administrators Subject: Re: FreeBSD 3.4 kernel configuration not automatically saved In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 3 Apr 2000, Richard Brooksby wrote: > We're setting up a machine to run FreeBSD 3.4. Until now we've been > running FreeBSD 2.x on various machines. We've noticed that the > kernel configuration (UserConfig, enabling/disabling device drivers > with "boot -c") doesn't persist between boots. > > Is this deliberate? > > If so, what is the approved way to save the configuration? (I > couldn't find anything about this in the handbook.) You apparently missed the well documented section of the handbook on compiling a custom kernel. :) Good luck, Doug -- "So, the cows were part of a dream that dreamed itself into existence? Is that possible?" asked the student incredulously. The master simply replied, "Mu." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message