From owner-freebsd-questions Mon Sep 20 7:11:42 1999 Delivered-To: freebsd-questions@freebsd.org Received: from easeway.com (ns1.easeway.com [209.69.39.1]) by hub.freebsd.org (Postfix) with ESMTP id 334F914E32 for ; Mon, 20 Sep 1999 07:11:39 -0700 (PDT) (envelope-from mwlucas@easeway.com) Received: (from mwlucas@localhost) by easeway.com (8.8.8/8.8.5) id JAA08468 for questions@freebsd.org; Mon, 20 Sep 1999 09:52:49 -0400 (EDT) Message-Id: <199909201352.JAA08468@easeway.com> Subject: kernel config and sysctl To: questions@freebsd.org Date: Mon, 20 Sep 1999 09:52:49 -0400 (EDT) From: mwlucas@exceptionet.com X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, doofus question time... I'm preparing an article on FreeBSD's sysctl interface -- not the inner workings, merely a "What is sysctl, and what is it good for?" piece. I've always had the impression that the sysctls available on a system are dependent on the kernel configuration, but have never been able to verify this. I've sat down a couple times and built a variety of kernels, trying to verify this with different combinations of options. Either I've been picking the wrong options, or the sysctls on a system are fixed. Can anyone confirm/deny this? What are some kernel options that carry along their own sysctl trees, if this is the case? Thanks, Michael -- Michael Lucas | Exceptionet, Inc. | www.exceptionet.com "Exceptional Networking" | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message