Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!zaphod.mps.ohio-state.edu!samsung!uunet!sci34hub!gary
From: gary@sci34hub.UUCP (Gary Heston)
Newsgroups: comp.unix.i386
Subject: Re: running setcolor script on bootup
Message-ID: <695@sci34hub.UUCP>
Date: 12 Jul 90 15:01:10 GMT
References: <1990Jul11.123256.939@nstar.uucp>
Reply-To: gary@sci34hub.sci.com (Gary Heston)
Organization: SCI Technology, Inc., Huntsville, Al.
Lines: 33

In article <1990Jul11.123256.939@nstar.uucp> larry@nstar.uucp (Larry Snyder) writes:
>yet placing this script in /etc/rc.d doesn't work since the
>consoles are not initiated as of yet - where could I put this
>script so that it executes right after the various consoles
>are initialized?

/etc/rc.d is a holding place for initializing scripts. They're executed
from /etc/rc0.d, or /etc/rc2.d, where they're linked to start or kill
names. Link your script in rc.d to rc2.d/S95script, and init will
execute it towards the end of setting up init level 2. The names in
the numbered rc.d directories follow the form:

   {KS}[00-99]name

Where:

	K or S indicates Kill or Start the process, daemon, etc.

	00-99 is a two-digit sequence number that init uses to 
		decide when each of the scripts is run.

	name  is a reference name for your convenience (acct, 
		sendmail, lp, etc.).

If you do a ls -i of /etc/rc.d and /etc/rc2.d, you'll find that
several are linked together.


-- 
    Gary Heston     { uunet!sci34hub!gary  }    System Mismanager
   SCI Technology, Inc.  OEM Products Department  (i.e., computers)
"The esteemed gentleman says I called him a liar. That's true, and I
regret it." Retief, a character created by Keith Laumer.