From owner-freebsd-arch Wed Jun 28 2:30:16 2000 Delivered-To: freebsd-arch@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id BA0F037B8E0 for ; Wed, 28 Jun 2000 02:30:13 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id 5E4A62DC10; Wed, 28 Jun 2000 11:36:03 +0200 (CEST) Received: by mx.webgiro.com (Postfix, from userid 1001) id DDD2C7818; Wed, 28 Jun 2000 11:25:41 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id DB90210E17 for ; Wed, 28 Jun 2000 11:25:41 +0200 (CEST) Date: Wed, 28 Jun 2000 11:25:39 +0200 (CEST) From: Andrzej Bialecki To: freebsd-arch@freebsd.org Subject: RFC: Dynamic sysctls, next round Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, http://www.freebsd.org/~abial/dyn_sysctl.tgz These patches provide support for fully dynamic sysctl manipulation. They are based on ideas of several people, including Arun Sharma, Jonathan Lemon and Doug Rabson. Thank you, guys! You can create and delete new sysctl_oid's at run time. There can be multiple users of subtrees (the oids keep a reference count). There is also a framework to help you keep track of already created oids (called 'context' - thanks to dfr for suggesting this!). These patches require fresh -current (as of 28 June 2000). You need to patch your /sys, then rebuild the kernel and restart with it. Then you should be able to load and unload example module that adds a couple of sysctl oids to the tree (check with sysctl -a). Please provide your comments. Thanks! 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-arch" in the body of the message