From owner-freebsd-questions Mon Apr 3 5:32:19 2000 Delivered-To: freebsd-questions@freebsd.org Received: from raven.ravenbrook.com (raven.ravenbrook.com [193.82.131.18]) by hub.freebsd.org (Postfix) with ESMTP id 97C4037BE01 for ; Mon, 3 Apr 2000 05:32:15 -0700 (PDT) (envelope-from rb@ravenbrook.com) Received: from [193.82.131.28] (skylark.ravenbrook.com [193.82.131.28]) by raven.ravenbrook.com (8.9.3/8.9.3) with ESMTP id NAA10960; Mon, 3 Apr 2000 13:32:03 +0100 (BST) Mime-Version: 1.0 X-Sender: rb@pop3.ravenbrook.com Message-Id: Date: Mon, 3 Apr 2000 13:31:49 +0100 To: freebsd-questions@freebsd.org From: Richard Brooksby Subject: FreeBSD 3.4 kernel configuration not automatically saved Cc: Ravenbrook System Administrators Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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.) Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message