All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] buggy init script
Date: Tue, 8 Mar 2016 00:21:42 +0100	[thread overview]
Message-ID: <56DE0D06.4020508@mind.be> (raw)
In-Reply-To: <CAK7rcp-mGsPNS03NthrhdGV00TtthChp0M+OP=oZ+7BW6isGzA@mail.gmail.com>

On 03/07/16 15:48, Kenneth Adam Miller wrote:
> I have /etc/init.d in my target directory being populated with relevant scripts
> S02abc, S90xyz, S91abcxyz, S92zyx. I operate under the belief that init.d
> contents get executed in order of their numbers after S, and that the names
> after S<num><name> do not matter.

  The scripts are actually run by /etc/init.d/rcS, so you can check there how it 
is done. Basically it will execute everything that starts with S in shell sort 
order.


  To debug things, the easiest thing to do is to change the shebang into
#! /bin/sh -x
which will print each command on the console before it is executed. Of course, 
that's assuming you have a console, otherwise things are more difficult to debug...


  Regards,
  Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

      parent reply	other threads:[~2016-03-07 23:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-07 14:48 [Buildroot] buggy init script Kenneth Adam Miller
2016-03-07 16:42 ` Steve Calfee
2016-03-07 23:21 ` Arnout Vandecappelle [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56DE0D06.4020508@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.