Date: Fri, 3 Oct 1997 01:00:40 -0500 (EST) From: "John S. Dyson" <toor@y.dyson.net> To: syssgm@dtir.qld.gov.au (Stephen McKay) Cc: pechter@lakewood.com, freebsd-hackers@FreeBSD.ORG, syssgm@dtir.qld.gov.au Subject: Re: Sysctl variables Message-ID: <199710030600.BAA06750@y.dyson.net> In-Reply-To: <199710020620.QAA20756@ogre.dtir.qld.gov.au> from Stephen McKay at "Oct 2, 97 04:20:56 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199710030600.BAA06750>