Return to BSD News archive
Newsgroups: comp.os.386bsd.development Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!zaphod.mps.ohio-state.edu!wupost!uunet!pipex!sunic!psinntp!psinntp!uuneo!sugar!peter From: peter@NeoSoft.com (Peter da Silva) Subject: Re: Some ideas on the driver interface (was: Re: Release of drivers etc.) Organization: NeoSoft Communications Services -- (713) 684-5900 Date: Fri, 12 Mar 1993 11:23:44 GMT Message-ID: <C3rwzL.Cs9@sugar.neosoft.com> References: <0bcN02Do3ab301@JUTS.ccc.amdahl.com> <C3qMGD.Ez7@unx.sas.com> <5biM02F.3aGG01@JUTS.ccc.amdahl.com> Lines: 31 In article <5biM02F.3aGG01@JUTS.ccc.amdahl.com> gab10@cd.amdahl.com (Gary A Browning) writes: > The /etc/rc script would recognize > all of the subdirectories through file name completion (something like > "/etc/rc.*/rc") and execute (actually source, I think) each file in turn. Actually, to be precise, System V has this useful concept of "run levels". Run level 0 is "shutdown", 1 is single-user, 2 is multi-user, 3 is network and applications (like at 3 the Oracle daemon would be running). You send the run level you want to "init", and it goes through the directory for the level you're going to and runs the startup (S*) scripts, or (if you're going to a lower level) kill (K*) scripts. Special run levels also existed (6 = reboot, for example). > This made it look like one large /etc/rc file but the structure was > more flexible for installing and removing packages. What we did on Xenix, which has the BSD type RC file, was simply create a single "rc.d" directory for the scripts. I'll be doing the same thing on my BSD system, kicking it off the local RC file, when I go full time. (I even set up an RC directory on my Amiga... it's a handy concept) I'd like to see something similar associated with drivers that needed special initialization commands. -- Peter da Silva. <peter@sugar.neosoft.com>. `-_-' Oletko halannut suttasi tänään? 'U` Tarjoilija, tämä ateria elää vielä.