From owner-freebsd-arch@FreeBSD.ORG  Fri Dec 28 22:57:25 2007
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 68DEE16A46B;
	Fri, 28 Dec 2007 22:57:25 +0000 (UTC)
	(envelope-from bright@elvis.mu.org)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
	by mx1.freebsd.org (Postfix) with ESMTP id 7646A13C45A;
	Fri, 28 Dec 2007 22:57:25 +0000 (UTC)
	(envelope-from bright@elvis.mu.org)
Received: by elvis.mu.org (Postfix, from userid 1192)
	id 1C8441A4D80; Fri, 28 Dec 2007 14:55:26 -0800 (PST)
Date: Fri, 28 Dec 2007 14:55:26 -0800
From: Alfred Perlstein <alfred@freebsd.org>
To: John Baldwin <jhb@freebsd.org>
Message-ID: <20071228225526.GJ76698@elvis.mu.org>
References: <200712271704.44796.jhb@FreeBSD.org>
	<200712281745.08144.jhb@freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200712281745.08144.jhb@freebsd.org>
User-Agent: Mutt/1.4.2.3i
Cc: freebsd-arch@freebsd.org
Subject: Re: kernel features MIB
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Dec 2007 22:57:25 -0000

* John Baldwin <jhb@freebsd.org> [071228 14:54] wrote:
> On Thursday 27 December 2007 05:04:44 pm John Baldwin wrote:
> > At work we don't have a pretty API for this at all, but I'm thinking for 
> > FreeBSD we can do this:
> > 
> > FEATURE(foo, "description of foo")
> > 
> > which is a macro to create the 'kern.features.foo' node and set it to 1.  Then 
> > we could have a routine in libc:
> > 
> > int	feature_present(const char *name);
> > 
> > That returns a boolean to indicate if a given feature is present or not by 
> > invoking sysctlbyname(3), etc.
> > 
> > Any objections to the idea?
> 
> So here's a bikeshed question I have no idea for.  Which header should
> feature_present()'s prototype go in?  I anticipate this routine being
> used in libc itself, so I don't think it can go into libutil.

Whereever sysconf/pathconf stuff is.

-- 
- Alfred Perlstein