Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Beattie <beattie@beattie-home.net>
To: buildroot@busybox.net
Subject: [Buildroot] my /etc/init.d/rcS won't run
Date: Fri, 01 Aug 2008 05:47:37 -0700	[thread overview]
Message-ID: <1217594857.6188.11.camel@kokopelli> (raw)
In-Reply-To: <4892BA2F.60606@cetrtapot.si>

On Fri, 2008-08-01 at 09:24 +0200, Hinko Kocevar wrote:
> Brian Beattie wrote:
> > I'm building a generic powerpc buildroot and it's all working as far as
> > I can tell, except the /etc/init.d/rcS will not run.  The line
> > "null::sysinit:/etc/init.d/rcS" is in /etc/inittab (I'm using
> > target/generic/target_skeleton/...).  Everything else in inittab seems
> > to be working and when I take the entries that mount /proc and all out
> > /proc does not get mounted.  When I run /etc/rcS it works fine.  The
> > permissions look OK.  I even put "echo $0>>/tag" as the first
> > executable line in the file, but rcS just does not want to run.
> > 
> > I'm baffeled, has anybody else run into this?
> 
> Is the /etc on the same partition as /bin, /sbin?
> 
> Can you post the error displayed? Also you might want to use this shabang
> 
> #!/bin/sh -x
> 
> in the /etc/init.d/rcS to see some debugging..

No errors, shell scripts would not run.

What I found was that including bash, caused /bin/sh to point to bash
and for dome reason bash does not want to run that early.  Currently
I've dropped bash.

> 
> HTH,
> Hinko
> 
-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting a bad thing?

Brian Beattie   LFS12947 | "Honor isn't about making the right choices.
beattie at beattie-home.net | It's about dealing with the consequences."
www.beattie-home.net     | -- Midori Koto

  reply	other threads:[~2008-08-01 12:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-31 22:36 [Buildroot] my /etc/init.d/rcS won't run Brian Beattie
2008-08-01  7:24 ` Hinko Kocevar
2008-08-01 12:47   ` Brian Beattie [this message]
2008-08-01 13:12     ` John Voltz
2008-08-01 14:27       ` Wade Berrier
2008-08-01 15:55         ` Marc Gauthier
2008-08-04 16:31           ` Wade Berrier

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=1217594857.6188.11.camel@kokopelli \
    --to=beattie@beattie-home.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox