From owner-freebsd-hackers  Thu Oct  2 23:05:45 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id XAA21154
          for hackers-outgoing; Thu, 2 Oct 1997 23:05:45 -0700 (PDT)
Received: from y.dyson.net (dyson.iquest.net [198.70.144.127])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA21138
          for <freebsd-hackers@FreeBSD.ORG>; Thu, 2 Oct 1997 23:05:20 -0700 (PDT)
Received: (from root@localhost)
	by y.dyson.net (8.8.7/8.8.5) id BAA06750;
	Fri, 3 Oct 1997 01:00:41 -0500 (EST)
From: "John S. Dyson" <toor@y.dyson.net>
Message-Id: <199710030600.BAA06750@y.dyson.net>
Subject: Re: Sysctl variables
In-Reply-To: <199710020620.QAA20756@ogre.dtir.qld.gov.au> from Stephen McKay at "Oct 2, 97 04:20:56 pm"
To: syssgm@dtir.qld.gov.au (Stephen McKay)
Date: Fri, 3 Oct 1997 01:00:40 -0500 (EST)
Cc: pechter@lakewood.com, freebsd-hackers@FreeBSD.ORG, syssgm@dtir.qld.gov.au
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> On Thursday, 2nd October 1997, Bill Pechter wrote:
> 
> >I'm copying this to -chat because I'm wondering if there's any user interest
> >in this except just me...
> >
> >I'm back working on the SysV init again. I know it's been a long layoff since
> >a number of you sent code to me to work on.  I've now got a dedicated test 
> >box and will be working hard on finishing the work that was started by 
> >a number of folks.
> >
> >Any chance of getting two varibles in the "official" FreeBSD sysctl MIB base..
> >
> >I was thinking of kern.run_level and kern.last_run_level.
> >I'd like to avoid homebrew kernel patches to do this (I don't think I want
> >to have to continually update the init code after each cvsup upgrade.)
> >
>
I'll sponsor those two variables.  I know that there are those who HATE
SYSV type init, but there are those who also NEED it.  As long as they don't
do anything, other than support a consistant interface for those who need
the SYSV init, then I don't see why there is a problem.  I don't think that
we can get into the habit of adding special variables into the kernel
sysctl database.  Things like SYSV init are special, and as long as I
don't get shouted down, I would like to allow and *support* optional use
of SYSV init.

John