[wplug] Hierarchical runlevels?

[Tom Rhodes]

On Mon, 30 Aug 2004 07:44:55 -0400
"Vanco, Don" <don.vanco at agilysys.com> wrote:

> 
> 
> >-----Original Message-----
> >From: wplug-bounces+don.vanco=agilysys.com at wplug.org 
> >[mailto:wplug-bounces+don.vanco=agilysys.com at wplug.org] On 
> >Behalf Of Bill Moran
> >Sent: Sunday, August 29, 2004 8:25 PM
> >To: General user list
> >Subject: Re: [wplug] Hierarchical runlevels?
> >
> >
> >Hagbard Celine <> wrote:
> >
> >> Not a Linux question, but input would be appreciated, anyway...
> >> 
> >> Does anyone remember if there is/was a system that set 
> >runlevels up as an
> >> hierarchy, i.e. a given runlevel would start the services 
> >defined for it, and
> >> the services in all levels below/above it?
> >> 
> >> I seem to have a vague recollection of such a thing...
> >
> >Solaris does something like this.  In that it has a "common" 
> >runlevel that
> >starts stuff no matter what runlevel the machine is at, then 
> >the config for
> >the appropriate runlevel is called as well.
> 	AFAIK pretty much all linux distros do this via rc.sysinit and /
> or rc.local or equivalent

If memory serves me correctly, HP-UX, AIX, Ultrix and Solaris
have a similar setup.  I *think* Linux just has symlinks to
their different runlevel directories.  NetBSD and FreeBSD have
a different rc setup than OpenBSD (since FreeBSD 5.X and NetBSD
X.X.X) where all scripts are stored in /etc/rc.d/ and started
with /etc/rc.conf or /etc/rc.conf.local[1].  I haven't had enough
experiance with OpenBSD to explain how it differs from the
other BSDs.  I do hope this helps, or perhaps I've misinterpreted
the question?

[1]: rc.conf.local is for backward compatibility and really should
     go away but AFAIR it will remain this way for some time.

-- 
Tom Rhodes