[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: [BusyBox] init applet "reverse order" config file?
From:       Allan Clark <allanc () sco ! com>
Date:       2002-09-30 15:15:03
[Download RAW message or body]

Erik;

Thanks for fixing the docs and getting back to me.

I saw in the code that you're taking pains to append to the end of the
list as you read a config file, and re-ordered my config file.

I guess I'm still getting used to busybox.  I'm also a "use init to
restart things" type of person rather than the ... err... unfortunate
/etc/rc.d/blah/blah/blah hierarchy of chewy nightmarish scripts now used
by many distros and commercial Unixes.

Thanks Erik.

Allan


Erik Andersen wrote:
> 
> On Thu Sep 26, 2002 at 03:12:33PM -0400, Allan Clark wrote:
> > BusyBox;
> >
> > I didn't see any discussion of this inthe last month's subject lines.
> > There is seems to be no way to search the archives.
> >
> > (Busybox 0.60.4, linux-2.4.19, full-blown libc and ld-linux)
> > >From the documentation:
> > (http://www.busybox.net/downloads/BusyBox.html)
> > >                 Unrecognized actions (like initdefault) will cause init to emit an
> > >                      error message, and then go along with its business.  All actions are
> > >                      run in the reverse order from how they appear in /etc/inittab.
> > >
> > >              <process>:
> 
> This used to be true.  But people found it confusing so I changed
> it, but I forgot to update the docs.  I just updated the docs in
> CVS.
> 
> > What order is the correct (ie intended) way?
> 
> The docs now read:
> 
>     "All actions are run in the order they appear in /etc/inittab"
> 
>  -Erik
> 
> --
> Erik B. Andersen             http://codepoet-consulting.com/
> --This message was written using 73% post-consumer electrons--
> _______________________________________________
> busybox mailing list
> busybox@busybox.net
> http://codepoet.org/mailman/listinfo/busybox

[prev in list] [next in list] [prev in thread] [next in thread]