From owner-freebsd-current@FreeBSD.ORG Tue May 23 21:22:27 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E55116B2B8; Tue, 23 May 2006 21:22:27 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 949D243D48; Tue, 23 May 2006 21:22:21 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.10.3.185] ([69.15.205.254]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k4NLMAv0011154; Tue, 23 May 2006 15:22:16 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <44737CFA.8070105@samsco.org> Date: Tue, 23 May 2006 15:22:02 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Warner Losh References: <44735620.9080403@samsco.org> <20060523.132355.21838169.imp@bsdimp.com> <447366CD.7010301@samsco.org> <20060523.145222.88564922.imp@bsdimp.com> In-Reply-To: <20060523.145222.88564922.imp@bsdimp.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-multimedia@freebsd.org, des@des.no, freebsd-current@freebsd.org, Alexander@Leidinger.net Subject: Re: Call for testing: emu10kx driver for Creative sound cards X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 21:22:29 -0000 Warner Losh wrote: >>giving. I'd really like to see namespaces and name prefixes defined >>that have stable/unstable meaning. I dropped this due to the very >>vocal opposition at the time. > > > Sounds like a good thing to me. If we document this (and the bit that > I sent in my other email) in sysctl(8), or somewhere more appropriate, > then I think we can do this. I propose that we put a single _ in > front of those sysctls that the author knows will go away and that no > code should be written to use them. this would give the unstable > namespace that you want and would be consistant with what _foo() > functions are for. Not sure if that means everything else is > permanant, however. I'm hoping this doesn't result in a bikeshed of > doom. > > Warner Sounds good. I guess what this means is that the entire sysctl namespace should be considered stable except for a set of defined areas. These defined areas will either be specifically designated and documented, or will have a '_' prefixing some element of their node name. Developers still have a responsibility to put proper thought into what they add into the stable namespace, and this space may be subject to change while the tree is marked "-CURRENT". However, once it is marked "-STABLE", it is stable and can only be changed by following appropriate deprecation procedures. For the purposes of documentation, it should be described that there are actually 3 types of nodes. There are stable, statically named nodes that will always exist on a running system. There are unstable, statically named nodes that may or may not exist from one release to another. And there are dynamic nodes that will exist depending on the devices, modules, and drivers present, and that these nodes may be stable or unstable depending on other attributes of the node name. Scott