Date: Wed, 1 Oct 1997 23:59:37 -0400 (EDT) From: Bill Pechter <pechter@lakewood.com> To: hackers@freebsd.org Cc: chat@freebsd.org Subject: Sysctl variables Message-ID: <199710020359.XAA00539@i4got.lakewood.com>
next in thread | raw e-mail | index | archive | help
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.) If they were standard in the kernel and blank, I think it would allow the SYSV init to be added as a package. This would make utmp changes unnecessary and be kind of slick. We'd be able to make both the BSD and SysV users happy. (I'm going to look at the userland command differences after this... including the ps, ls differences. I still haven't given up on the idea of supporting dual universes and getting tools up to support Unixware and SCO commercial packages.) This is kind of like the Pyramid OS/x System -- they shipped with both the SysV and BSD init programs and a script that will enable either one and save the old rc scripts and init files in the event of a reinstall of the other init. Bill ------------------------------------------------------------------------------ Bill Pechter | 17 Meredith Drive Tinton Falls, NJ 07724 | 908-389-3592 pechter@lakewood.com | Save computing history, give an old geek old hardware. This msg brought to you by the letters PDP and the number 11.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199710020359.XAA00539>