From owner-freebsd-current Thu Dec 9 9: 9: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id 3A2CB1565B for ; Thu, 9 Dec 1999 09:09:04 -0800 (PST) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id 13C302DC07; Thu, 9 Dec 1999 18:09:45 +0100 (CET) Received: by mx.webgiro.com (Postfix, from userid 1001) id B7D127811; Thu, 9 Dec 1999 18:06:41 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id B5DE810E10 for ; Thu, 9 Dec 1999 18:06:41 +0100 (CET) Date: Thu, 9 Dec 1999 18:06:41 +0100 (CET) From: Andrzej Bialecki To: freebsd-current@freebsd.org Subject: Modules and sysctl tree Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'd like to know whether we reached some conclusions concerning the naming of sysctl variables created (or related to) KLDs. I know that Linux emulator creates "compat.linux". I don't know if any other module creates sysctls (well, except my SPY module.. :-). So, what is the current thinking? Should we use modules.my_module.whatever, or kld.my_kld.whatever, or just sprinkle the new sysctls randomly over the tree, according to their functions, e.g. kern.my_module_kern_hook net.inet.my_module_inet_hook ... Also, it seems that you cannot create new sysctls (leaves and nodes) at runtime, i.e. after the module has been loaded. 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-current" in the body of the message