From owner-freebsd-hackers  Mon Apr 16 13:36:49 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from CPE-61-9-164-106.vic.bigpond.net.au (CPE-61-9-138-241.vic.bigpond.net.au [61.9.138.241])
	by hub.freebsd.org (Postfix) with ESMTP id B261837B43E
	for <hackers@freebsd.org>; Mon, 16 Apr 2001 13:36:45 -0700 (PDT)
	(envelope-from darrenr@reed.wattle.id.au)
Received: (from root@localhost)
	by CPE-61-9-164-106.vic.bigpond.net.au (8.11.0/8.11.0) id f3GKaiB04723
	for <hackers@freebsd.org>; Tue, 17 Apr 2001 06:36:44 +1000 (EST)
From: Darren Reed <darrenr@reed.wattle.id.au>
Message-Id: <200104162036.GAA25344@avalon.reed.wattle.id.au>
Subject: User-defined bit in sysctl flags ?
To: hackers@freebsd.org
Date: Tue, 17 Apr 2001 06:36:21 +1000 (EST)
X-Mailer: ELM [version 2.4ME+ PL37 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


What do people think about having a range of bits in oid_kind that are
not used by FreeBSD but are only to be used by ``private'' sysctl handlers?

e.g.

#define	CTLFLAG_PRIVATE	0x000ffff0

Do I need elaborate any further ?

Darren

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message