From owner-freebsd-hackers Mon Sep 8 17:58:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA20800 for hackers-outgoing; Mon, 8 Sep 1997 17:58:32 -0700 (PDT) Received: from shell.firehouse.net (brian@shell.firehouse.net [209.42.203.45]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA20789 for ; Mon, 8 Sep 1997 17:58:25 -0700 (PDT) Received: from localhost (brian@localhost) by shell.firehouse.net (8.8.5/8.8.5) with SMTP id UAA27542; Mon, 8 Sep 1997 20:58:07 -0400 (EDT) Date: Mon, 8 Sep 1997 20:58:05 -0400 (EDT) From: Brian Mitchell To: Preferred Customer cc: "hackers@FreeBSD.ORG" Subject: Re: sysctl In-Reply-To: <01BCBC8F.DE28EAE0@d7.dial-22.mbo.ma.ultra.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 8 Sep 1997, Preferred Customer wrote: > > I was looking at sysctl,h and kern_sysctl.c the other day and I was wondering why there where no predefined > > Sysctl_short() aka CTLTYPE_SHORT or > Sysctl_char() aka CTLTYPE_CHAR (note: not string seems to me that SYSCTL_INT() covers both of these. I'm using SYSCTL_INT in cases where i only need on/off values, it isn't too bad :). > > Definitions. > > It seems to me that short and char have to be at lease as worthy to be included as atomic types as quad. > Also, shouldn't there be support for octet string, as in a not necessarily print-able sequence of unsigned char (a not uncommon mib occurance) > - > g > > You could add some of this with SYSCTL_PROC fairly easily.