From owner-freebsd-hackers Thu Nov 19 21:48:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18530 for freebsd-hackers-outgoing; Thu, 19 Nov 1998 21:48:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ren.dtir.qld.gov.au (ns.dtir.qld.gov.au [203.108.138.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18523 for ; Thu, 19 Nov 1998 21:48:12 -0800 (PST) (envelope-from syssgm@dtir.qld.gov.au) Received: by ren.dtir.qld.gov.au; id PAA04904; Fri, 20 Nov 1998 15:46:25 +1000 (EST) Received: from ogre.dtir.qld.gov.au(167.123.8.3) by ren.dtir.qld.gov.au via smap (3.2) id xma004888; Fri, 20 Nov 98 15:46:05 +1000 Received: from atlas.dtir.qld.gov.au (atlas.dtir.qld.gov.au [167.123.8.9]) by ogre.dtir.qld.gov.au (8.8.8/8.8.7) with ESMTP id PAA22824; Fri, 20 Nov 1998 15:46:05 +1000 (EST) Received: from nymph.dtir.qld.gov.au (nymph.dtir.qld.gov.au [167.123.10.10]) by atlas.dtir.qld.gov.au (8.8.5/8.8.5) with ESMTP id PAA27640; Fri, 20 Nov 1998 15:46:04 +1000 (EST) Received: from nymph.dtir.qld.gov.au (localhost.dtir.qld.gov.au [127.0.0.1]) by nymph.dtir.qld.gov.au (8.8.8/8.8.7) with ESMTP id PAA25250; Fri, 20 Nov 1998 15:46:02 +1000 (EST) (envelope-from syssgm@nymph.dtir.qld.gov.au) Message-Id: <199811200546.PAA25250@nymph.dtir.qld.gov.au> To: Bill/Carolyn Pechter cc: freebsd-hackers@FreeBSD.ORG, syssgm@dtir.qld.gov.au Subject: Re: SysV Init References: <199811191220.HAA09760@shell.monmouth.com> In-Reply-To: <199811191220.HAA09760@shell.monmouth.com> from Bill/Carolyn Pechter at "Thu, 19 Nov 1998 07:20:51 -0500" Date: Fri, 20 Nov 1998 15:46:02 +1000 From: Stephen McKay Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 19th November 1998, Bill/Carolyn Pechter wrote: > On Wed, 18 Nov 1998, Chuck Robey wrote: >Boy did I get flames when I proposed this. Perfectly understandable. Wish I could think of some good personal attacks, but flaming isn't really my style. Instead, I'll beseech thee to refrain from consorting with the Dark One. >This is one area where SysV is superior. Woah! Put me down as absolutely against this position. Put my face on your dart board, if you must! >> I'm asking for a system where the legacy rc is there for those who want ^^^^^^ "Legacy" in this case is a nasty word. It's not legacy as far as I am concerned. It is the current and best practice. I would be bitterly disappointed if it was downgraded to a compatibility option on a SysV style init system. >> it (and would probably be installed by default) but a system of >> run-levels and rc.d type stuff would be feasible. Such a thing could >> then even be a port. I think such an approach would short-circuit most >> of the complaints, and let the idea move forward with coding. > >I was looking to do this as a port of the SysV init, getty and >hopefully one day package tools. If we got SVR4 or Solaris X86 >emulation we'd be set. > >My plan was two sysctl variables for current and past run state. >This would avoid the need for a utmp change. > >kern.current_runlevel >kern.prev_runlevel > >The who command would also be need modified to support who -R and >read the kern.current_runlevel variable. > >I was thinking about porting getty_ps over along with gettydefs... > >Anyone spot anything else we'd need to do for compatibility? I'll take the lateral view on this and assume you mean compatibility with existing practice. :-) I hope that any additions you make will not cause any *requirement* to use run levels for any purpose whatsoever. Optional use among consenting adults is hard to stop. And another thing... Oops, they're turning off the network for the building relocation. Oh well, you'll have to wait for later before I can tell you how much grief the SysV init system has given me over the years. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message